Re: [fossil-users] [v123 - Windows] Timeline view does not respect CRLF's in commit comments?
Thanks Themba, I will give that a try. Sorry to hear CRLF's are not preserved... :( Are they purposely deleted or ignored at comment loading or are they dropped by the html render? I paste multi-line text into the commit prompt and my DOS window retains the line breaks. I keep a History text document of revisions and notes for this purpose. At each commit, I paste in the latest comments intended for the next release. It would help the users read the Timeline easier if the LineBreaks didn't go away. Thanks for your help. On Sun, Sep 30, 2012 at 11:17 PM, Themba Fletcher themba.fletc...@gmail.com wrote: 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 brs 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 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 ___ 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?
I thought that the setting Themba recommended (admin timeline Allow block markup in timeline setting) allowed you to use the fossil markup language in your comments. Part of that means that single line breaks are ignored, while double linebreaks are interpreted as new paragraphs - http://www.fossil-scm.org/xfer/wiki_rules. I might be remembering that wrong As to when they are dropped, I don't know. The logic is probably somewhere here: http://www.fossil-scm.org/xfer/artifact/2f7437d0e0c8559f1ee648f4714e626b9910112a Tomek Date: Mon, 1 Oct 2012 21:09:17 -0400 From: sky5w...@gmail.com To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] [v123 - Windows] Timeline view does not respect CRLF's in commit comments? Thanks Themba, I will give that a try. Sorry to hear CRLF's are not preserved... :( Are they purposely deleted or ignored at comment loading or are they dropped by the html render? I paste multi-line text into the commit prompt and my DOS window retains the line breaks. I keep a History text document of revisions and notes for this purpose. At each commit, I paste in the latest comments intended for the next release. It would help the users read the Timeline easier if the LineBreaks didn't go away. Thanks for your help. On Sun, Sep 30, 2012 at 11:17 PM, Themba Fletcher themba.fletc...@gmail.com wrote: 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 brs 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 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 ___ 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
Re: [fossil-users] [v123 - Windows] Timeline view does not respect CRLF's in commit comments?
Thanks for the links Tomek. While I don't understand the wiki logic, I am not going to fight it. It is not a value add for me to keep 2 lists(1 single-spaced and 1 double-spaced) just to conform to the wiki rules. However, if I un-select ... [ ] Allow block-markup in timeline why would the default logic be to drop CRLF's? Pasting multi-line comments seems so simple, yet quite frustrating. Thanks for the info. On Mon, Oct 1, 2012 at 9:48 PM, Tomek Kott tkott.li...@outlook.com wrote: I thought that the setting Themba recommended (admin timeline Allow block markup in timeline setting) allowed you to use the fossil markup language in your comments. Part of that means that single line breaks are ignored, while double linebreaks are interpreted as new paragraphs - http://www.fossil-scm.org/xfer/wiki_rules. I might be remembering that wrong As to when they are dropped, I don't know. The logic is probably somewhere here: http://www.fossil-scm.org/xfer/artifact/2f7437d0e0c8559f1ee648f4714e626b9910112a Tomek Date: Mon, 1 Oct 2012 21:09:17 -0400 From: sky5w...@gmail.com To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] [v123 - Windows] Timeline view does not respect CRLF's in commit comments? Thanks Themba, I will give that a try. Sorry to hear CRLF's are not preserved... :( Are they purposely deleted or ignored at comment loading or are they dropped by the html render? I paste multi-line text into the commit prompt and my DOS window retains the line breaks. I keep a History text document of revisions and notes for this purpose. At each commit, I paste in the latest comments intended for the next release. It would help the users read the Timeline easier if the LineBreaks didn't go away. Thanks for your help. On Sun, Sep 30, 2012 at 11:17 PM, Themba Fletcher themba.fletc...@gmail.com wrote: 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 brs 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 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 ___ 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] [v123 - Windows] Timeline view does not respect CRLF's in commit comments?
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?
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 brs 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 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
