{"thread":{"id":"54939","subject":"Re: git tag truncates tag list","startedAt":"2021-01-05T17:12:58Z","lastAt":"2021-01-05T17:12:58Z","messageCount":1,"participants":["stratus@tuta.io"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"413471","messageId":"MQIXBhC--3-2@tuta.io","threadId":"54939","inReplyTo":null,"subject":"Re: git tag truncates tag list","fromName":"","fromEmail":"stratus@tuta.io","sentAt":"2021-01-05T17:12:06Z","receivedAt":"2021-01-05T17:12:58Z","isPatch":false,"sender":{"key":"stratus@tuta.io","avatar":null},"body":"Yes, sorry, they are there, it is only the sort order placing the newest ones further up in the list. Using page down to go down the long list of numerous screenfuls, the missing ones were not shown on the final screen so I didn't see them, and it ended at 5.9-rc8 instead of going to 5.10 and 5.11 as I had expected. I thought perhaps there was some limit on the number of tags shown, but couldn't find any reference to a limit searching online, and less itself can display long man pages without problem.\n\ngit --no-pager tag\nshows the same thing\necho $LESS\necho $GIT_PAGER\ngit config core.pager\ngit config pager.tag\n\nAll return nothing.\n\necho $PAGER\nless\nChanging PAGER to more uses more for git tag instead, but gives the same result. So this was indeed using less as the pager.\n\nThank you for the helpful answers, I've only used git with smaller repos before and hadn't encountered that effect previously.\n"}]}