Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

I don't know about what commands to paginate by default, but no to versionable settings for this. Don't want to force this on others. On Mar 23, 2017 4:08 PM, "Christophe Gouiran" wrote: > Good morning, > > I would like to implement the feature given in the title. > I'm

[fossil-users] [PATCH] Makes NORETURN macro meaningful for msvc

Good morning, When I compile Fossil revision [f21820f4] with Visual C++ 2010 I get following warning: import.c(1275) : warning C4715: 'svn_handle_symlinks' : not all control paths return a value Although, at line 1270 there is: fossil_fatal("Too short symbolic link path"); which is a NORETURN

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

I vote that the pagination be off by default to preserve the existing behaviour -- terminals have been able to scroll for decades now so I don't know why systemd/git like to do this by default but it is REALLY annoying having to pipe EVERYTHING through "cat" to defeat it. (Also, even better

[fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

Good morning, I would like to implement the feature given in the title. I'm inspired by what Git (by default ?) and Mercurial (with Pager extension activated) do. I'd like to avoid typing "fossil | less" everytime I notice it produces an

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

I think there should be a single setting, pager-command, which the pager uses for *all* command-line output if it defined. The setting defaults to an empty string, which means no pagination. I don't think you want to select some subset of commands to be paginated. Do them all, or do none of