Jean-Marc Lasgouttes wrote:
So this patch would be OK for trunk and branch?
Yes. Note, however, the typo below.
Jürgen
Index: src/paragraph_funcs.h
===
--- src/paragraph_funcs.h (révision 20407)
+++
Jean-Marc Lasgouttes wrote:
> So this patch would be OK for trunk and branch?
Yes. Note, however, the typo below.
Jürgen
> Index: src/paragraph_funcs.h
> ===
> --- src/paragraph_funcs.h (révision 20407)
> +++
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
Actually, it could be renamed to something like
break-paragraph-special, or an 'inverse' option could be added to
break-paragraph.
Yes, the current name is certainly misleading.
I would prefer to merge the two lfuns and add an option (I don't
Jean-Marc Lasgouttes wrote:
Ideas include:
break-paragraph special
break-paragraph inverse
break-paragraph alt
break-paragraph 1
So, what name shall I give to this thing?
From these, inverse is surely the least confusing one.
Jürgen
Juergen Spitzmueller [EMAIL PROTECTED] writes:
So, what name shall I give to this thing?
From these, inverse is surely the least confusing one.
So this patch would be OK for trunk and branch?
JMarc
svndiff src lib/bind
Index: src/LyXAction.cpp
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
>> Actually, it could be renamed to something like
>> break-paragraph-special, or an 'inverse' option could be added to
>> break-paragraph.
>
> Yes, the current name is certainly misleading.
> I would prefer to merge the two lfuns and add an option
Jean-Marc Lasgouttes wrote:
> Ideas include:
>
> break-paragraph special
> break-paragraph inverse
> break-paragraph alt
> break-paragraph 1
>
> So, what name shall I give to this thing?
>From these, inverse is surely the least confusing one.
Jürgen
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>> So, what name shall I give to this thing?
>
> From these, inverse is surely the least confusing one.
So this patch would be OK for trunk and branch?
JMarc
svndiff src lib/bind
Index: src/LyXAction.cpp
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
Jean-Marc Lasgouttes wrote:
The behaviour of M-Return is the exact symmetry of what Return would
do:
I see. I'm fine with that (though I still prefer the old behaviour, i.e. swap
Return and M-Return).
Could you be more precise? I do not think
Jean-Marc Lasgouttes wrote:
Could you be more precise? I do not think the behaviour of Return has
been changed recently. What would you like to see?
I'm referring to the old behaviour where M-return was necessary to preserve
the nesting level.
I'm not sure I like this. Why should we double
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
Jean-Marc Lasgouttes wrote:
Could you be more precise? I do not think the behaviour of Return has
been changed recently. What would you like to see?
I'm referring to the old behaviour where M-return was necessary to preserve
the nesting level.
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
Jean-Marc Lasgouttes wrote:
Bu currently with environments (itemize, etc.) both return and
M-return keep the nesting level.
Yes (which is bad).
How do you go to a lower level usually?
M-S-leftarrow.
Which is less fun than pressing Return
Jean-Marc Lasgouttes wrote:
Bu currently with environments (itemize, etc.) both return and
M-return keep the nesting level.
Yes (which is bad).
How do you go to a lower level usually?
M-S-leftarrow.
Jürgen
Jean-Marc Lasgouttes wrote:
Which is less fun than pressing Return repeatedly, you'll admit :)
Well, let's say you get used to it ...
So, what would be your preferred behaviour?
Let's forget about my (personal) preferred behaviour (I am obviously a
minority here).
I think your patch is a
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Jean-Marc Lasgouttes wrote:
>> The behaviour of M-Return is the exact symmetry of what Return would
>> do:
>
> I see. I'm fine with that (though I still prefer the old behaviour, i.e. swap
> Return and M-Return).
Could you be more precise? I do
Jean-Marc Lasgouttes wrote:
> Could you be more precise? I do not think the behaviour of Return has
> been changed recently. What would you like to see?
I'm referring to the old behaviour where M-return was necessary to preserve
the nesting level.
> > I'm not sure I like this. Why should we
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Jean-Marc Lasgouttes wrote:
>> Could you be more precise? I do not think the behaviour of Return has
>> been changed recently. What would you like to see?
>
> I'm referring to the old behaviour where M-return was necessary to preserve
> the
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Jean-Marc Lasgouttes wrote:
>> Bu currently with environments (itemize, etc.) both return and
>> M-return keep the nesting level.
>
> Yes (which is bad).
>
>> How do you go to a lower level usually?
>
> M-S-.
Which is less fun than pressing
Jean-Marc Lasgouttes wrote:
> Bu currently with environments (itemize, etc.) both return and
> M-return keep the nesting level.
Yes (which is bad).
> How do you go to a lower level usually?
M-S-.
Jürgen
Jean-Marc Lasgouttes wrote:
> Which is less fun than pressing Return repeatedly, you'll admit :)
Well, let's say you get used to it ...
> So, what would be your preferred behaviour?
Let's forget about my (personal) preferred behaviour (I am obviously a
minority here).
I think your patch is a
Jean-Marc Lasgouttes wrote:
The behaviour of M-Return is the exact symmetry of what Return would
do:
I see. I'm fine with that (though I still prefer the old behaviour, i.e. swap
Return and M-Return).
Actually, it could be renamed to something like
break-paragraph-special, or an 'inverse'
Jean-Marc Lasgouttes wrote:
> The behaviour of M-Return is the exact symmetry of what Return would
> do:
I see. I'm fine with that (though I still prefer the old behaviour, i.e. swap
Return and M-Return).
> Actually, it could be renamed to something like
> break-paragraph-special, or an
Jean-Marc Lasgouttes wrote:
Here is a patch that implements proper functionning of M-Return (at
least as I see it: like Return, but inverting role of environment and
non-environment). I'd be interested to have some feedback on it. This
is potentially for trunk and branch.
Could you describe
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
Jean-Marc Lasgouttes wrote:
Here is a patch that implements proper functionning of M-Return (at
least as I see it: like Return, but inverting role of environment and
non-environment). I'd be interested to have some feedback on it. This
is
Jean-Marc Lasgouttes wrote:
> Here is a patch that implements proper functionning of M-Return (at
> least as I see it: like Return, but inverting role of environment and
> non-environment). I'd be interested to have some feedback on it. This
> is potentially for trunk and branch.
Could you
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Jean-Marc Lasgouttes wrote:
>> Here is a patch that implements proper functionning of M-Return (at
>> least as I see it: like Return, but inverting role of environment and
>> non-environment). I'd be interested to have some feedback on it. This
>>
Jean-Marc Lasgouttes schrieb:
M-Return is supposed to be do for commands what Return would do for
Environments and do for environments what Return would do for
commands.
However, I see now that it does not do anything interesting for
enumerations. I'll have to double check that.
Here is a
> Jean-Marc Lasgouttes schrieb:
>> M-Return is supposed to be do for commands what Return would do for
>> Environments and do for environments what Return would do for
>> commands.
>>
>> However, I see now that it does not do anything interesting for
>> enumerations. I'll have to double check
28 matches
Mail list logo