You shouldn't do that.
Do not take auto-increment unique identifier as an ordinal number.
Word unique means that the identifier should be stuck with it's row forever
There is no connection between these numbers and enumerating.
Imagine you want to select records in alphabetical order. Where would your precious numbers go?
A database is not like ordered list, as you probably think. It is not a flat file with ordered rows. It has totally different ideology. Rows in the database do not have any order. And take order only at select time, if it was excpicitly set by ORDER BY clause.
Also, database is supposed to do a search and filtering for you. So, with selected rows and different ordering this auto-increment number has nothing to do with real rows positions.
If you want to enumerate output - it is presentation layer job. Just add a counter on the PHP side.
And again: these numbers supposed to identify a certain record. If you change this number, you'd never find your record again.
Take Stackoverflow as an example. SO identifies questions with such a number:
stackoverflow.com/questions/3132439/mysql-auto-decrementing-value
So, imagine you saved this page address to a bookmark. Now Jeff comes along and renumber the whole database. You press your bookmark and land on the different question. Whole site would be a terrible mess.
Remember: Renumbering unique identifiers is evil!