[fossil-users] [v123 - Windows] Timeline view does not respect CRLF's in commit comments?

2012-09-30 Thread sky5walk
Hi, searched email history and couldn't find an answer...
Admittedly, this is a nitpick but I really want my Timeline view to
retain the comments I enter at commit time.
Ex.
# Since no default text editor is set using EDITOR or VISUAL
# environment variables or the "fossil set editor" command,
# and because no check-in comment was specified using the "-m"
# or "-M" command-line options, you will need to enter the
# check-in comment below.  Type "." on a line by itself when
# you are done:
2012.09.30
  1) Changed this...
  2) Broke that...
.
New_Version: d742fd95965ddb1a4f2d6bba36247a9f01d22a86

fossil ui SHOWS THIS Timeline...
22:23   
[d742fd9596] Leaf: 2012.09.30 1) Changed this... 2) Broke that...
(user: sky5walk, tags: trunk)

INSTEAD OF:
22:23   
[d742fd9596] Leaf: 2012.09.30
1) Changed this...
2) Broke that...
(user: sky5walk, tags: trunk)


Thanks for Fossil!
___
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] [v123 - Windows] Timeline view does not respect CRLF's in commit comments?

2012-09-30 Thread Themba Fletcher
I've not seen or heard of a way to do what you asked for, and I went
on a hunt for just that about a year ago.

You can, if you wish, visit admin:timeline in the ui and check "allow
block markup ..."

This will let you use s and such in your commit messages, but the
raw HTML will still show up in the cli timeline.

(This next bit is slightly preachy - my apologies in advance)

I've found over time that this limitation has caused me to habitually
use the -m flag with an inline commit message. This has limited my
commits to only what I can describe in one line, and forced me into a
workflow where I use small branches much more frequently, grouping
small changes Into coherent sets.

I can't say whether this limitation is by design or by happy accident
-- but either way it has resulted in my using fossil in a more
structured way, giving me a better and cleaner picture of my code over
time. So a net win for me.

Best regards,

Themba



On Sep 30, 2012, at 19:43, "sky5w...@gmail.com"  wrote:

> Hi, searched email history and couldn't find an answer...
> Admittedly, this is a nitpick but I really want my Timeline view to
> retain the comments I enter at commit time.
> Ex.
> # Since no default text editor is set using EDITOR or VISUAL
> # environment variables or the "fossil set editor" command,
> # and because no check-in comment was specified using the "-m"
> # or "-M" command-line options, you will need to enter the
> # check-in comment below.  Type "." on a line by itself when
> # you are done:
> 2012.09.30
>  1) Changed this...
>  2) Broke that...
> .
> New_Version: d742fd95965ddb1a4f2d6bba36247a9f01d22a86
>
> fossil ui SHOWS THIS Timeline...
> 22:23
> [d742fd9596] Leaf: 2012.09.30 1) Changed this... 2) Broke that...
> (user: sky5walk, tags: trunk)
>
> INSTEAD OF:
> 22:23
> [d742fd9596] Leaf: 2012.09.30
> 1) Changed this...
> 2) Broke that...
> (user: sky5walk, tags: trunk)
>
>
> Thanks for Fossil!
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users