John Levon <[EMAIL PROTECTED]> writes:
| On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
|
| > Why? If you have already entered something without pressing "Execute"
| > (return) then you should be allowe to edit this furter before doing
| > so.
|
| Because status messages can appear inb
Phew! What a correspondence!
I do use emacs a lot, so I'm used to the behaviour that Lars is proposing.
However, am I right in saying, Lars, that you've decided the only way to gain
focus in the menubar is to type M-x because that's the only way you could get
the LyX core to know what's happen
On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> Why? If you have already entered something without pressing "Execute"
> (return) then you should be allowe to edit this furter before doing
> so.
Because status messages can appear inbetween, as we've already mentioned.
I don't want to de
John Levon <[EMAIL PROTECTED]> writes:
| On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
|
| > John Levon <[EMAIL PROTECTED]> writes:
| >
| > | On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
| > |
| > | > Are you able to enter commands there then and have them executed?
| > |
On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> |
> | > Are you able to enter commands there then and have them executed?
> |
> | ok, I'm talking crap. The problem is after a M-x, I
John Levon <[EMAIL PROTECTED]> writes:
| On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
|
| > Are you able to enter commands there then and have them executed?
|
| ok, I'm talking crap. The problem is after a M-x, I can take the focus
| away from the minibuffer and do other things. But
On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> Are you able to enter commands there then and have them executed?
ok, I'm talking crap. The problem is after a M-x, I can take the focus
away from the minibuffer and do other things. But this doesn't reset
the editibility of the mb. I.e.
John Levon <[EMAIL PROTECTED]> writes:
| On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
|
| > | then forever more I can focus on the minibuffer with the mouse. What is the
| > | meaning of this keypress ? It acts like "permanently unlock the minibuffer".
| >
| > that is a bug then.
|
John Levon <[EMAIL PROTECTED]> writes:
| On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
|
| > | then forever more I can focus on the minibuffer with the mouse. What is the
| > | meaning of this keypress ? It acts like "permanently unlock the minibuffer".
| >
| > that is a bug then.
|
On 24 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> | then forever more I can focus on the minibuffer with the mouse. What is the
> | meaning of this keypress ? It acts like "permanently unlock the minibuffer".
>
> that is a bug then.
... and this bug implements a feature that you say is
John Levon <[EMAIL PROTECTED]> writes:
| On 23 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
|
| > John Levon <[EMAIL PROTECTED]> writes:
| >
| > | > were allowed to "click into" the minibuffer. (then the minibufer would
| > | > have to know about lyxfuncs etc...)
| > | >
| > | > M-x is yo
On 23 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | > were allowed to "click into" the minibuffer. (then the minibufer would
> | > have to know about lyxfuncs etc...)
> | >
> | > M-x is your friend.
> |
> | I'm now very confused. Because I jus
John Levon <[EMAIL PROTECTED]> writes:
| > were allowed to "click into" the minibuffer. (then the minibufer would
| > have to know about lyxfuncs etc...)
| >
| > M-x is your friend.
|
| I'm now very confused. Because I just started CVS lyx up again, and now I
| /can/ click in the minibuffer. I
On 23 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> true.. that feature has been removed.
>
> Now operations of the minibuffer is controlled from lfuns, this makes
> a much better structure. And I don't see how this could be done if you
> were allowed to "click into" the minibuffer. (then
John Levon <[EMAIL PROTECTED]> writes:
| On 23 May 2001, Jean-Marc Lasgouttes wrote:
|
| > > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| >
| > Lars> Are there other issues that I have not thought of?
| >
| > Sometimes senseless messages get into the minibuffer. For example,
On 23 May 2001, Jean-Marc Lasgouttes wrote:
> > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Lars> Are there other issues that I have not thought of?
>
> Sometimes senseless messages get into the minibuffer. For example, if
> you do a 'Update dvi' on the userguide, you get
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
Lars> > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: | |
Lars> Lars> Are there other issues that I have not thought of? | |
Lars> Sometimes senseless messages
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Are there other issues that I have not thought of?
|
| Sometimes senseless messages get into the minibuffer. For example, if
| you do a 'Update dvi' on the userguide, you
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Are there other issues that I have not thought of?
Sometimes senseless messages get into the minibuffer. For example, if
you do a 'Update dvi' on the userguide, you get
ull3 (message ull3)(message ull3)
which is probably not
John Levon <[EMAIL PROTECTED]> writes:
| it is how some completions in some programs work.
and I don't like it... you might have to tab for a long time to find
the lfun that you are looking for...
| > What _I_ would like is a box popping out where I could select the
| > lyxfun I want. I
On 23 May 2001, Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
[...]
> | if we're talking UI, I'd like it to default to the first match, then you
> | can cycle through with . Or something.
>
> Of coursre the bad thing about this is that we have to keep state...
> and suddenly
On 23 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> Of coursre the bad thing about this is that we have to keep state...
> and suddenly TAB will have two distinct actions: completion and
> next... not sure if I like that.
it is how some completions in some programs work.
> What _I
John Levon <[EMAIL PROTECTED]> writes:
| On 23 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
|
| > Not sure...
| > I guess it depend upon if the last char is significant of not.
|
| well I certainly don't know :)
|
| > Not quite...
| >
| > A couple of issues:
| > - How to handle
On 23 May 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> Not sure...
> I guess it depend upon if the last char is significant of not.
well I certainly don't know :)
> Not quite...
>
> A couple of issues:
> - How to handle completion? Currently it just outputs all the
> choi
John Levon <[EMAIL PROTECTED]> writes:
| Why do LyXText::NumberOf[Label]HFills differ from NumberOfSEparators
| in the loop termination, i.e. one has
|
| p < last
|
| the others have
|
| p <= last
|
| is this right ?
Not sure...
I guess it depend upon if the last char is significant of not.
25 matches
Mail list logo
