Re: Lab manual
Hello Nirmal, it's propably not that important... but as you asked: On Mon, 24 Nov 2003 00:31:43 -0500 Nirmal Govind [EMAIL PROTECTED] wrote: My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to I've been a bit inprecise: 1. enter the text with standard layout Here at depth 0 ist missing, meaning I start writing without any red bars at the left. 2. chose the layouts for every paragraph Now I make then lyx-code or description or whatever... 3. indent them to their final places ... and indent them (S-M-Right) to the depth where they should go to. And as I like examples: example A nice paragraph in std layout at depth 0 Another nice paragraph in std layout at depth 0 /example becomes example' 1. A nice Paragraph now in enumeration layout at depth 0 A nice paragraph in lyxcode layout at depth 0 /example' becomes example'' 1. A nice Paragraph in enumeration layout at depth 0 | A nice paragraph in lyxcode layout now at depth 1 /example'' I'm not sure I understand.. Hopefully it's a bit clearer now. To me the main advantage of my approach is that during the input of the text one hasn't to care about keeping the right depth. currently, if the instructions on the wiki page are followed, one does not get what is shown in the screenshot. Yes you're right. But that has nothing to do with the above :) It's not a difference between M Enter and C Enter as far as I can tell cos you'll get the second block of code in text mode which doesn't seem to be what that example tries to illustrate (or so I figure.. :-)).. I must admit I didn't follow the instructions but simply did as I do always :-/ need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code Probably not but just to stay consistent, i.e. to not confuse someone who follows the instructions and sees return arrows at the end of the lines while the screenshot doesn't have them... You're right :) Maybe I find the time to create a new screenshot. Karsten
Re: Lab manual
On Sun, 23 Nov 2003, Nirmal Govind wrote: Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate Hi Christian.. I think there's something missing in those instructions: Thanks, you're right and I've fixed it now. Hopefully it's correct now... /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
On Mon, 24 Nov 2003, Karsten Heymann wrote: On Sun, 23 Nov 2003 17:05:45 -0500 Nirmal Govind [EMAIL PROTECTED] wrote: That remembers me of a litte Idea I had: Is it possible to map C-S-Enter to the following command sequence: M-Enter (or it's lfun counterpart) S-M-Right (increase depth) chose standard layout In my bind files I nowhere found a Key mapped to more than one lfun. is this possible at all? Sure... they're called command-sequences, see http://wiki.lyx.org/pmwiki.php/Tips/CommandSequences I'm not sure if C-S-Enter is separate from C-Enter, but if it isn't you could try mapping it to M-C-Enter? /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
On Mon, 24 Nov 2003, Karsten Heymann wrote: Probably not but just to stay consistent, i.e. to not confuse someone who follows the instructions and sees return arrows at the end of the lines while the screenshot doesn't have them... You're right :) Maybe I find the time to create a new screenshot. Please don't update the screenshot, I've modified the description :-) /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
Hopefully it's a bit clearer now. To me the main advantage of my approach is that during the input of the text one hasn't to care about keeping the right depth. Totally clear! :-) Thanks... And thanks Christian for updating the webpage.. nirmal
Re: Lab manual
Hello Nirmal, it's propably not that important... but as you asked: On Mon, 24 Nov 2003 00:31:43 -0500 Nirmal Govind [EMAIL PROTECTED] wrote: My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to I've been a bit inprecise: 1. enter the text with standard layout Here at depth 0 ist missing, meaning I start writing without any red bars at the left. 2. chose the layouts for every paragraph Now I make then lyx-code or description or whatever... 3. indent them to their final places ... and indent them (S-M-Right) to the depth where they should go to. And as I like examples: example A nice paragraph in std layout at depth 0 Another nice paragraph in std layout at depth 0 /example becomes example' 1. A nice Paragraph now in enumeration layout at depth 0 A nice paragraph in lyxcode layout at depth 0 /example' becomes example'' 1. A nice Paragraph in enumeration layout at depth 0 | A nice paragraph in lyxcode layout now at depth 1 /example'' I'm not sure I understand.. Hopefully it's a bit clearer now. To me the main advantage of my approach is that during the input of the text one hasn't to care about keeping the right depth. currently, if the instructions on the wiki page are followed, one does not get what is shown in the screenshot. Yes you're right. But that has nothing to do with the above :) It's not a difference between M Enter and C Enter as far as I can tell cos you'll get the second block of code in text mode which doesn't seem to be what that example tries to illustrate (or so I figure.. :-)).. I must admit I didn't follow the instructions but simply did as I do always :-/ need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code Probably not but just to stay consistent, i.e. to not confuse someone who follows the instructions and sees return arrows at the end of the lines while the screenshot doesn't have them... You're right :) Maybe I find the time to create a new screenshot. Karsten
Re: Lab manual
On Sun, 23 Nov 2003, Nirmal Govind wrote: Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate Hi Christian.. I think there's something missing in those instructions: Thanks, you're right and I've fixed it now. Hopefully it's correct now... /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
On Mon, 24 Nov 2003, Karsten Heymann wrote: On Sun, 23 Nov 2003 17:05:45 -0500 Nirmal Govind [EMAIL PROTECTED] wrote: That remembers me of a litte Idea I had: Is it possible to map C-S-Enter to the following command sequence: M-Enter (or it's lfun counterpart) S-M-Right (increase depth) chose standard layout In my bind files I nowhere found a Key mapped to more than one lfun. is this possible at all? Sure... they're called command-sequences, see http://wiki.lyx.org/pmwiki.php/Tips/CommandSequences I'm not sure if C-S-Enter is separate from C-Enter, but if it isn't you could try mapping it to M-C-Enter? /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
On Mon, 24 Nov 2003, Karsten Heymann wrote: Probably not but just to stay consistent, i.e. to not confuse someone who follows the instructions and sees return arrows at the end of the lines while the screenshot doesn't have them... You're right :) Maybe I find the time to create a new screenshot. Please don't update the screenshot, I've modified the description :-) /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
Hopefully it's a bit clearer now. To me the main advantage of my approach is that during the input of the text one hasn't to care about keeping the right depth. Totally clear! :-) Thanks... And thanks Christian for updating the webpage.. nirmal
Re: Lab manual
Hello Nirmal, it's propably not that important... but as you asked: On Mon, 24 Nov 2003 00:31:43 -0500 "Nirmal Govind" <[EMAIL PROTECTED]> wrote: > > My personal opinion on this is that keeping depth with M-Enter can sometimes > > be unhandy. I prefer to I've been a bit inprecise: > > 1. enter the text with "standard" layout Here "at depth 0" ist missing, meaning I start writing without any red bars at the left. > > 2. chose the layouts for every paragraph Now I make then "lyx-code" or "description" or whatever... > > 3. indent them to their final places ... and indent them (S-M-Right) to the depth where they should go to. And as I like examples: A nice paragraph in std layout at depth 0 Another nice paragraph in std layout at depth 0 becomes1. A nice Paragraph now in enumeration layout at depth 0 A nice paragraph in lyxcode layout at depth 0 becomes 1. A nice Paragraph in enumeration layout at depth 0 | A nice paragraph in lyxcode layout now at depth 1 > I'm not sure I understand.. Hopefully it's a bit clearer now. To me the main advantage of my approach is that during the input of the text one hasn't to care about keeping the right depth. > currently, if the instructions on the wiki > page are followed, one does not get what is shown in the screenshot. Yes you're right. But that has nothing to do with the above :) > It's not a difference between M Enter and C Enter as far as I can tell > cos you'll get the second block of code in text mode which doesn't seem > to be what that example tries to illustrate (or so I figure.. :-)).. I must admit I didn't follow the instructions but simply did as I do always :-/ > >>need to be modified and the C-Enter replaced with M-Enter. > > > > > > Does that make a difference (apart from empty lines being ignored in lyx-code > > > > Probably not but just to stay consistent, i.e. to not confuse someone > who follows the instructions and sees return arrows at the end of the > lines while the screenshot doesn't have them... You're right :) Maybe I find the time to create a new screenshot. Karsten
Re: Lab manual
On Sun, 23 Nov 2003, Nirmal Govind wrote: > > > Um.. if you mean something like in the screenshot at this page > > http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate > > > > Hi Christian.. I think there's something missing in those instructions: > Thanks, you're right and I've fixed it now. Hopefully it's correct now... /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
On Mon, 24 Nov 2003, Karsten Heymann wrote: > On Sun, 23 Nov 2003 17:05:45 -0500 > "Nirmal Govind" <[EMAIL PROTECTED]> wrote: > > That remembers me of a litte Idea I had: Is it possible to map C-S-Enter to > the following command sequence: > M-Enter (or it's lfun counterpart) > S-M-Right (increase depth) > chose "standard" layout > In my bind files I nowhere found a Key mapped to more than one lfun. is this > possible at all? Sure... they're called command-sequences, see http://wiki.lyx.org/pmwiki.php/Tips/CommandSequences I'm not sure if C-S-Enter is separate from C-Enter, but if it isn't you could try mapping it to M-C-Enter? /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
On Mon, 24 Nov 2003, Karsten Heymann wrote: > > Probably not but just to stay consistent, i.e. to not confuse someone > > who follows the instructions and sees return arrows at the end of the > > lines while the screenshot doesn't have them... > > You're right :) Maybe I find the time to create a new screenshot. > Please don't update the screenshot, I've modified the description :-) /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
Hopefully it's a bit clearer now. To me the main advantage of my approach is that during the input of the text one hasn't to care about keeping the right depth. Totally clear! :-) Thanks... And thanks Christian for updating the webpage.. nirmal
Lab manual
I need to create a book that includes hundreds of lab exercises for students. Many exercises are formatted with steps as in this nonsense example: 1. Connect to the Internet and download ... Here's an example of how to do this: lynx http://www.blahblah.com/... Be sure to . 2. Untar the file with a command similar to this: tar xzvf carnivore-1.2.tar.gz 3. You must now compile the program. ... using a command similar to this: ./configure --prefix=/opt/carnivore Is there a document class that comes close to this? Ed Sawicki
Re: Lab manual
On Sun, 23 Nov 2003, Ed Sawicki wrote: I need to create a book that includes hundreds of lab exercises for students. Many exercises are formatted with steps as in this nonsense example: 1. Connect to the Internet and download ... Here's an example of how to do this: lynx http://www.blahblah.com/... Be sure to . 2. Untar the file with a command similar to this: tar xzvf carnivore-1.2.tar.gz 3. You must now compile the program. ... using a command similar to this: ./configure --prefix=/opt/carnivore Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate you don't need a document class for it. /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate Hi Christian.. I think there's something missing in those instructions: increase the depth (M-p Right) and then write and change it to followed by M-Enter so that we don't change the depth. We now have: Now write foo --widget=blah, C-Enter, foo --widget=blah and Enter. We now have: Before the last line above, shouldn't there be a change to the LyX-code environment with a M-p c and then an M-p Right to get the same depth as the first set of LyX-code text? If I do the above what's quoted above, I get foo --widget=blah in text mode aligned with and change it to. Secondly, to get what Karsten has on the screenshot, the two lines which look like the following: Then write foo --widget=blub and use C-Enter to get a new line, where you write bar /dev/null and press need to be modified and the C-Enter replaced with M-Enter. nirmal
Re: Lab manual
On Sun, 23 Nov 2003 17:05:45 -0500 Nirmal Govind [EMAIL PROTECTED] wrote: Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate Hi Christian.. I think there's something missing in those instructions: increase the depth (M-p Right) and then write and change it to followed by M-Enter so that we don't change the depth. We now have: My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to 1. enter the text with standard layout 2. chose the layouts for every paragraph 3. indent them to their final places But I think that's mainly a matter of taste (that's why I didn't add it to the wiki page). Secondly, to get what Karsten has on the screenshot, the two lines which look like the following: Then write foo --widget=blub and use C-Enter to get a new line, where you write bar /dev/null and press need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code when done with (M-)Enter instead of C-Enter)? I didn't use them cause I feel they have a certain stigma on them as being untypographical(?) ... That remembers me of a litte Idea I had: Is it possible to map C-S-Enter to the following command sequence: M-Enter (or it's lfun counterpart) S-M-Right (increase depth) chose standard layout In my bind files I nowhere found a Key mapped to more than one lfun. is this possible at all? Reason for wanting this: Adding a paragraph inside an enumeration or itemization easily: 1. kjanskjndkc nlfkjvn ljkfdnv jkafndvjkanfdv kjhnadsk cjhaldjvh ljfakjklfdv S-M-Enter kjdslkhb lhfdlvhdlfvjh ljkhfbl jkshdflvjkhfv lkjsdflksdjf l kdjlkjl 2. jkjhs kdjfh I believe it's simple but my (few) tries failed... good night everyone, Karsten
Re: Lab manual
My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to 1. enter the text with standard layout 2. chose the layouts for every paragraph 3. indent them to their final places I'm not sure I understand.. currently, if the instructions on the wiki page are followed, one does not get what is shown in the screenshot. It's not a difference between M Enter and C Enter as far as I can tell cos you'll get the second block of code in text mode which doesn't seem to be what that example tries to illustrate (or so I figure.. :-)).. need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code Probably not but just to stay consistent, i.e. to not confuse someone who follows the instructions and sees return arrows at the end of the lines while the screenshot doesn't have them... nirmal
Lab manual
I need to create a book that includes hundreds of lab exercises for students. Many exercises are formatted with steps as in this nonsense example: 1. Connect to the Internet and download ... Here's an example of how to do this: lynx http://www.blahblah.com/... Be sure to . 2. Untar the file with a command similar to this: tar xzvf carnivore-1.2.tar.gz 3. You must now compile the program. ... using a command similar to this: ./configure --prefix=/opt/carnivore Is there a document class that comes close to this? Ed Sawicki
Re: Lab manual
On Sun, 23 Nov 2003, Ed Sawicki wrote: I need to create a book that includes hundreds of lab exercises for students. Many exercises are formatted with steps as in this nonsense example: 1. Connect to the Internet and download ... Here's an example of how to do this: lynx http://www.blahblah.com/... Be sure to . 2. Untar the file with a command similar to this: tar xzvf carnivore-1.2.tar.gz 3. You must now compile the program. ... using a command similar to this: ./configure --prefix=/opt/carnivore Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate you don't need a document class for it. /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate Hi Christian.. I think there's something missing in those instructions: increase the depth (M-p Right) and then write and change it to followed by M-Enter so that we don't change the depth. We now have: Now write foo --widget=blah, C-Enter, foo --widget=blah and Enter. We now have: Before the last line above, shouldn't there be a change to the LyX-code environment with a M-p c and then an M-p Right to get the same depth as the first set of LyX-code text? If I do the above what's quoted above, I get foo --widget=blah in text mode aligned with and change it to. Secondly, to get what Karsten has on the screenshot, the two lines which look like the following: Then write foo --widget=blub and use C-Enter to get a new line, where you write bar /dev/null and press need to be modified and the C-Enter replaced with M-Enter. nirmal
Re: Lab manual
On Sun, 23 Nov 2003 17:05:45 -0500 Nirmal Govind [EMAIL PROTECTED] wrote: Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate Hi Christian.. I think there's something missing in those instructions: increase the depth (M-p Right) and then write and change it to followed by M-Enter so that we don't change the depth. We now have: My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to 1. enter the text with standard layout 2. chose the layouts for every paragraph 3. indent them to their final places But I think that's mainly a matter of taste (that's why I didn't add it to the wiki page). Secondly, to get what Karsten has on the screenshot, the two lines which look like the following: Then write foo --widget=blub and use C-Enter to get a new line, where you write bar /dev/null and press need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code when done with (M-)Enter instead of C-Enter)? I didn't use them cause I feel they have a certain stigma on them as being untypographical(?) ... That remembers me of a litte Idea I had: Is it possible to map C-S-Enter to the following command sequence: M-Enter (or it's lfun counterpart) S-M-Right (increase depth) chose standard layout In my bind files I nowhere found a Key mapped to more than one lfun. is this possible at all? Reason for wanting this: Adding a paragraph inside an enumeration or itemization easily: 1. kjanskjndkc nlfkjvn ljkfdnv jkafndvjkanfdv kjhnadsk cjhaldjvh ljfakjklfdv S-M-Enter kjdslkhb lhfdlvhdlfvjh ljkhfbl jkshdflvjkhfv lkjsdflksdjf l kdjlkjl 2. jkjhs kdjfh I believe it's simple but my (few) tries failed... good night everyone, Karsten
Re: Lab manual
My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to 1. enter the text with standard layout 2. chose the layouts for every paragraph 3. indent them to their final places I'm not sure I understand.. currently, if the instructions on the wiki page are followed, one does not get what is shown in the screenshot. It's not a difference between M Enter and C Enter as far as I can tell cos you'll get the second block of code in text mode which doesn't seem to be what that example tries to illustrate (or so I figure.. :-)).. need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code Probably not but just to stay consistent, i.e. to not confuse someone who follows the instructions and sees return arrows at the end of the lines while the screenshot doesn't have them... nirmal
Lab manual
I need to create a book that includes hundreds of lab exercises for students. Many exercises are formatted with steps as in this nonsense example: 1. Connect to the Internet and download ... Here's an example of how to do this: lynx http://www.blahblah.com/... Be sure to . 2. Untar the file with a command similar to this: tar xzvf carnivore-1.2.tar.gz 3. You must now compile the program. ... using a command similar to this: ./configure --prefix=/opt/carnivore Is there a document class that comes close to this? Ed Sawicki
Re: Lab manual
On Sun, 23 Nov 2003, Ed Sawicki wrote: > I need to create a book that includes hundreds of lab exercises > for students. Many exercises are formatted with steps as in this > nonsense example: > > 1. Connect to the Internet and download ... Here's an example of >how to do this: > >lynx http://www.blahblah.com/... > >Be sure to . > > 2. Untar the file with a command similar to this: > >tar xzvf carnivore-1.2.tar.gz > > 3. You must now compile the program. ... using a command >similar to this: > >./configure --prefix=/opt/carnivore > Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate you don't need a document class for it. /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Lab manual
Um.. if you mean something like in the screenshot at this page http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate Hi Christian.. I think there's something missing in those instructions: "increase the depth (M-p Right) and then write "and change it to" followed by M-Enter so that we don't change the depth. We now have: Now write "foo --widget=blah", C-Enter, "foo --widget=blah" and Enter. We now have:" Before the last line above, shouldn't there be a change to the LyX-code environment with a M-p c and then an M-p Right to get the same depth as the first set of LyX-code text? If I do the above what's quoted above, I get "foo --widget=blah" in text mode aligned with "and change it to". Secondly, to get what Karsten has on the screenshot, the two lines which look like the following: "Then write "foo --widget=blub" and use C-Enter to get a new line, where you write "bar > /dev/null" and press" need to be modified and the C-Enter replaced with M-Enter. nirmal
Re: Lab manual
On Sun, 23 Nov 2003 17:05:45 -0500 "Nirmal Govind" <[EMAIL PROTECTED]> wrote: > > > Um.. if you mean something like in the screenshot at this page > > http://wiki.lyx.org/pmwiki.php/Tips/MultipleLyxCodeInSingleEnumerate > > > > Hi Christian.. I think there's something missing in those instructions: > > "increase the depth (M-p Right) and then write "and change it to" > followed by M-Enter so that we don't change the depth. We now have: > > My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to 1. enter the text with "standard" layout 2. chose the layouts for every paragraph 3. indent them to their final places But I think that's mainly a matter of taste (that's why I didn't add it to the wiki page). > Secondly, to get what Karsten has on the screenshot, the two lines which > look like the following: > > "Then write "foo --widget=blub" and use C-Enter to get a new line, where > you write "bar > /dev/null" and press" > > need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code when done with (M-)Enter instead of C-Enter)? I didn't use them cause I feel they have a certain "stigma" on them as being untypographical(?) ... That remembers me of a litte Idea I had: Is it possible to map C-S-Enter to the following command sequence: M-Enter (or it's lfun counterpart) S-M-Right (increase depth) chose "standard" layout In my bind files I nowhere found a Key mapped to more than one lfun. is this possible at all? Reason for wanting this: Adding a paragraph inside an enumeration or itemization easily: 1. kjanskjndkc nlfkjvn ljkfdnv jkafndvjkanfdv kjhnadsk cjhaldjvh ljfakjklfdv kjdslkhb lhfdlvhdlfvjh ljkhfbl jkshdflvjkhfv lkjsdflksdjf l kdjlkjl 2. jkjhs kdjfh I believe it's simple but my (few) tries failed... good night everyone, Karsten
Re: Lab manual
My personal opinion on this is that keeping depth with M-Enter can sometimes be unhandy. I prefer to 1. enter the text with "standard" layout 2. chose the layouts for every paragraph 3. indent them to their final places I'm not sure I understand.. currently, if the instructions on the wiki page are followed, one does not get what is shown in the screenshot. It's not a difference between M Enter and C Enter as far as I can tell cos you'll get the second block of code in text mode which doesn't seem to be what that example tries to illustrate (or so I figure.. :-)).. need to be modified and the C-Enter replaced with M-Enter. Does that make a difference (apart from empty lines being ignored in lyx-code Probably not but just to stay consistent, i.e. to not confuse someone who follows the instructions and sees return arrows at the end of the lines while the screenshot doesn't have them... nirmal