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

2017-03-27 Thread Ross Berteig
On 3/27/2017 2:29 PM, Christophe Gouiran wrote: Someone wanting to get the list or current branch without relying on raw Fossil output could use "fossil json branch list" for that purpose. But only if fossil was configured with JSON support. Which is not configured by default, or in the

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

2017-03-27 Thread Christophe Gouiran
> > > 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 Pytho

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

2017-03-27 Thread Warren Young
On Mar 27, 2017, at 12:07 PM, Warren Young wrote: > > It isn’t always clue to newbies s/clue/clear/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

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

2017-03-27 Thread Marc Simpson
On Mon, Mar 27, 2017 at 10:40 AM, Christophe Gouiran wrote: > > please find an attached patch which implements a new "current" subcommand for > "branch". > This is now the default subcommand if one executes "fossil branch" without > any subcommand. While the addition of a subcommand seems like

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

2017-03-27 Thread Warren Young
On Mar 27, 2017, at 11:50 AM, bch wrote: > > > executing "fossil branch" to get the current branch is not very convenient > > to me. > > Note that "fossil info" gives information about the current checkout, > including the branch name. That info is also given in “fossil status”, a command you

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

2017-03-27 Thread bch
On Mar 27, 2017 10:40, "Christophe Gouiran" wrote: 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. Note that "fossil info" gives

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

2017-03-27 Thread Umgeher Torgersen
Nice! -- //twitter: @umgeher //xmpp: m...@umgeher.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

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

2017-03-27 Thread Christophe Gouiran
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 "bran