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

Reply via email to