Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Stephan Beal
On Mon, May 27, 2013 at 6:51 PM, Richard Hipp wrote: > On Mon, May 27, 2013 at 12:47 PM, wrote: > >> Thanks but I see no changes to my Timeline comments? >> >> > Your browser might have the old CSS cached. Try pressing Reload. > Also try adding !important to the css: white-space: pre !importa

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
SuperAwesome! Thanks Isaac and for this topic. It's like someone cleaned my windshield :)) Wow, another one of my fossil thorns removed so easily. Thanks for fossil! On Mon, May 27, 2013 at 2:35 PM, Isaac Jurado wrote: > Replying sky5w...@gmail.com: > > > > I am using fossil v1.25[80bf94e0f7] i

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Isaac Jurado
Replying sky5w...@gmail.com: > > I am using fossil v1.25[80bf94e0f7] if that might explain further. Yes, that explains it. The use of was added here: http://fossil-scm.org/index.html/info/f9d4e0853b6650294117fd08683aa8358983f974 Which is two months after the version you're running. In your ve

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
Ok, I get same results with Chrome or IE. Even though the edit pane displays [LF]'s, the html source did not show any within the text section? I'll monitor this thread to see if any CSS gurus can explain? Thanks for trying. On Mon, May 27, 2013 at 1:23 PM, Richard Hipp wrote: > > > On Mon, May

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 1:20 PM, wrote: > I am using fossil v1.25[80bf94e0f7] if that might explain further. > > Probably not because none of this has changed in ages. Press Ctrl-U on the timeline page in your browser (Firefox and Chrome - dunno about others) and see what HTML is coming across.

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
I am using fossil v1.25[80bf94e0f7] if that might explain further. On Mon, May 27, 2013 at 1:18 PM, wrote: > Ahh! Very cool. > The manifest shows my [CRLF]'s were compressed to [LF]'s = /n, but no > matter. The edit window shows the line feeds properly. > Wish I could get that to cascade to my

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
Ahh! Very cool. The manifest shows my [CRLF]'s were compressed to [LF]'s = /n, but no matter. The edit window shows the line feeds properly. Wish I could get that to cascade to my Timeline view? On Mon, May 27, 2013 at 1:08 PM, Richard Hipp wrote: > > > On Mon, May 27, 2013 at 1:04 PM, wrote:

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 1:04 PM, wrote: > Just to be explicit, my comments are loaded without markups but do > contain [CRLF]'s. > I am unsure of the presence of my original [CRLF]'s within the timeline > data? > On the web interface, go to the screen that shows a check-in that contains CRLFs in

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
Just to be explicit, my comments are loaded without markups but do contain [CRLF]'s. I am unsure of the presence of my original [CRLF]'s within the timeline data? I also tried 'span.timeline...' with no effect. Should this work on previously loaded comments or only newly added ones? This would be

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 12:57 PM, wrote: > Yes, I tried that. > Should there be a prefix to the .timelineComment? > I did: "span.timelineComment ..". Maybe that makes a difference. I'm not very knowledgeable about CSS. > .timelineComment { > font-family: monospace; > white-space: pre; >

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
Yes, I tried that. Should there be a prefix to the .timelineComment? .timelineComment { font-family: monospace; white-space: pre; } I noticed 'white-space: pre;' is used in other places in the CSS. On Mon, May 27, 2013 at 12:51 PM, Richard Hipp wrote: > > > On Mon, May 27, 2013 at 12:47 PM,

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 12:47 PM, wrote: > Thanks but I see no changes to my Timeline comments? > > > Your browser might have the old CSS cached. Try pressing Reload. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lis

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
Thanks but I see no changes to my Timeline comments? On Mon, May 27, 2013 at 12:40 PM, Isaac Jurado wrote: > On Mon, May 27, 2013 at 6:36 PM, wrote: > > > > "On the web interface, all of the commit message are displayed inside of > > So you can perhaps adjust the > > look of comments to

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Isaac Jurado
On Mon, May 27, 2013 at 6:36 PM, wrote: > > "On the web interface, all of the commit message are displayed inside of > So you can perhaps adjust the > look of comments to your liking by editing the CSS and without having to > touch code." > > This has been a long time nuisance for me. Can

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread sky5walk
"On the web interface, all of the commit message are displayed inside of So you can perhaps adjust the look of comments to your liking by editing the CSS and without having to touch code." This has been a long time nuisance for me. Can someone provide a CSS example enabling my [CR+LF]'s with

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 11:44 AM, Stephan Beal wrote: > On Mon, May 27, 2013 at 5:37 PM, Isaac Jurado wrote: > >> P.S: Apparently, the command line timeline also joins all the message >> into a single line. I still have to look through the code to see if >> it's done at commit/import time or jus

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Stephan Beal
On Mon, May 27, 2013 at 5:37 PM, Isaac Jurado wrote: > P.S: Apparently, the command line timeline also joins all the message > into a single line. I still have to look through the code to see if > it's done at commit/import time or just at rendering. > It's done in src/comformat.c:comment_print

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 11:37 AM, Isaac Jurado wrote: > > P.S: Apparently, the command line timeline also joins all the message > into a single line. I still have to look through the code to see if > it's done at commit/import time or just at rendering. > > Fossil preserves the commit message te

Re: [fossil-users] Git import newlines in comments

2013-05-27 Thread Isaac Jurado
On Mon, May 27, 2013 at 2:46 AM, Richard Hipp wrote: > > On Sun, May 26, 2013 at 8:39 PM, Richard Collins > wrote: >> >> I'm looking at switching a git repository to fossil. >> >> I've done an export and import and found that fossil is not showing the >> newlines from the commit messages. >> >> e

Re: [fossil-users] Git import newlines in comments

2013-05-26 Thread Richard Hipp
On Sun, May 26, 2013 at 8:39 PM, Richard Collins wrote: > I'm looking at switching a git repository to fossil. > > I've done an export and import and found that fossil is not showing the > newlines from the commit messages. > > e.g. the commit message > > Fix slow PDF thumbnail generation > > Squa

[fossil-users] Git import newlines in comments

2013-05-26 Thread Richard Collins
I'm looking at switching a git repository to fossil. I've done an export and import and found that fossil is not showing the newlines from the commit messages. e.g. the commit message Fix slow PDF thumbnail generation Squashed commit of the following: commit 350fe7521e79a914a54ff384b6ca02a66d5b