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 d...@sqlite.org wrote: On Sun, May 26, 2013 at 8:39 PM, Richard Collins richa...@richardc.net 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

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 dipto...@gmail.com 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

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 dipto...@gmail.com 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

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 sgb...@googlemail.comwrote: On Mon, May 27, 2013 at 5:37 PM, Isaac Jurado dipto...@gmail.com 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

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 span class='timelineComment'.../span. 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

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

2013-05-27 Thread Isaac Jurado
On Mon, May 27, 2013 at 6:36 PM, sky5w...@gmail.com wrote: On the web interface, all of the commit message are displayed inside of span class='timelineComment'.../span. So you can perhaps adjust the look of comments to your liking by editing the CSS and without having to touch code. This

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 dipto...@gmail.com wrote: On Mon, May 27, 2013 at 6:36 PM, sky5w...@gmail.com wrote: On the web interface, all of the commit message are displayed inside of span

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

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 12:47 PM, sky5w...@gmail.com 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

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 d...@sqlite.org wrote: On Mon, May 27, 2013

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

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 12:57 PM, sky5w...@gmail.com 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;

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 1:04 PM, sky5w...@gmail.com 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

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 d...@sqlite.org wrote: On Mon, May 27, 2013 at 1:04

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

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 1:20 PM, sky5w...@gmail.com 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

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 d...@sqlite.org wrote:

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 span class=timelineComment was added here: http://fossil-scm.org/index.html/info/f9d4e0853b6650294117fd08683aa8358983f974 Which is two months after the version

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 dipto...@gmail.com wrote: Replying sky5w...@gmail.com: I am using fossil

[fossil-users] Handling renames on import

2013-05-27 Thread Isaac Jurado
Hello, I'm testing Fossil by migrating a bunch of Mercurial repositories. Unlike Git, Mercurial tracks file renames. However, in order to create a Fossil repository I have to follow the Mercurial - Git - Fossil path. On the first conversion I lose file copying/renaming information. But the git

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 d...@sqlite.org wrote: On Mon, May 27, 2013 at 12:47 PM, sky5w...@gmail.com 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:

Re: [fossil-users] Handling renames on import

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 3:35 PM, Isaac Jurado dipto...@gmail.com wrote: Hello, I'm testing Fossil by migrating a bunch of Mercurial repositories. Unlike Git, Mercurial tracks file renames. However, in order to create a Fossil repository I have to follow the Mercurial - Git - Fossil path.

Re: [fossil-users] Handling renames on import

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 3:45 PM, Richard Hipp d...@sqlite.org wrote: On Mon, May 27, 2013 at 3:35 PM, Isaac Jurado dipto...@gmail.com wrote: Hello, I'm testing Fossil by migrating a bunch of Mercurial repositories. Unlike Git, Mercurial tracks file renames. However, in order to create a

Re: [fossil-users] Handling renames on import

2013-05-27 Thread Richard Hipp
On Mon, May 27, 2013 at 3:35 PM, Isaac Jurado dipto...@gmail.com wrote: Hello, I'm testing Fossil by migrating a bunch of Mercurial repositories. Unlike Git, Mercurial tracks file renames. However, in order to create a Fossil repository I have to follow the Mercurial - Git - Fossil path.

Re: [fossil-users] Handling renames on import

2013-05-27 Thread Isaac Jurado
Wow, I didn't expect this attention. Let me reply in detail. I'm testing Fossil by migrating a bunch of Mercurial repositories. Unlike Git, Mercurial tracks file renames. However, in order to create a Fossil repository I have to follow the Mercurial - Git - Fossil path. Is there a better