Re: [fossil-users] [PROPOSED FEATURE] Fossil 'branch' command displays only current branch by default

> > > While the addition of a subcommand seems like a good idea, changing > default behaviour will no doubt break existing workflows. > I agree on this point. However I have learned (where possible) to never rely on raw commands outputs in my wrappers. Indeed, I took over several years ago a

[fossil-users] [PROPOSED FEATURE] Fossil 'branch' command displays only current branch by default

Hello everybody, Amount of branches may be quite important (in Fossil code itself, there are now about 100 branches). In this case, executing "fossil branch" to get the current branch is not very convenient to me. please find an attached patch which implements a new "current" subcommand for

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

Please find as attached file another patch which: 1. First test for a real terminal before spawning the pager command. 2. No more paginate json command. I see that most of you complain about this proposed feature. It was only a proposition, if it is not accepted I won't care. However, it

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

Hi all, First of all many thanks for all your feedback. I come back to you with an implemented solution. After many thinking, for me not all commands need to send their outputs to a pager. Only ones which may output a big amount of lines in a bunch. Therefore, I selected only some of them to be

[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

[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