[RFC] Re: short and long log messages

[John Arbash Meinel]

Alexander Belchenko wrote:
> Matthieu Moy пишет:
>> To make it easier for users to type everything on a command line
>> (multi-line shell commands are possible, but rarely comfortable), I can
>> see two solutions :
>>
>> * Add another option, like Arch did (-m "foo" --body "bar")
>>
>> * Allow \n in the message for a line break, like echo does.
>>
>> The second one will probably please C programmers and old unix users,
>> but the first is more explicit to people not having this culture.
> 
> I think support both is will be very good. I understand explicitness of
> first variant, but personally I'm prefer to use second.
> 
> -- 
> Alexander

Well, in bash, doing this works:

bzr commit -m "Summary line<CR>
more text
and still more
and a little bit more
"

Bash holds the command request open until the " is closed. (It works for
both " and ')

However, I don't know how to spawn a bzr command like
	:!bzr commit -m "stuff for commit"
in vim which would wrap lines.

I'm a 'commit -m' user like Robert. When I commit, I don't even want to
take the time to spawn a text editor. Though I suppose if "bzr commit"
included the status output, then I wouldn't have to do "bzr status; bzr
commit -m ..."

Ultimately, though, if we change the behavior of 'bzr log --line' then
we should still have it restrict the output based on number of
characters. Because there will be lots of entries like Robert's or mine
which are a single long line. And the nice thing about --line is that it
doesn't wrap.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060518/05abd9f8/attachment.pgp