Le 22/08/2016 à 19:34, Richard Heck a écrit :
Richard, this is candidate for branch.
OK.
Thanks, done now.
JMarc
On 08/22/2016 12:22 PM, Jean-Marc Lasgouttes wrote:
> Le 20/08/2016 à 00:24, Pavel Sanda a écrit :
>>> Is the following what you had in mind? I have no idea of how people use
>>> minibuffer, so please test if you care.
>>
>> This is indeed the behaviour
Le 20/08/2016 à 00:24, Pavel Sanda a écrit :
Is the following what you had in mind? I have no idea of how people use
minibuffer, so please test if you care.
This is indeed the behaviour I would expect. Pavel
Thanks for confirmation. It is in master at [65b0e84b/lyxgit].
Richard
Jean-Marc Lasgouttes wrote:
> Le 19/07/2016 ? 09:56, Scott Kostyshak a écrit :
>> if I open the minibuffer, then click into the work area, and then
>> execute alt+x, I expect the focus to switch to the mini-buffer (just as
>> it does if the mini-buffer is not open). Is that
Le 19/07/2016 à 09:56, Scott Kostyshak a écrit :
if I open the minibuffer, then click into the work area, and then
execute alt+x, I expect the focus to switch to the mini-buffer (just as
it does if the mini-buffer is not open). Is that a correct expectation?
Is the following what you had
Le 12/08/2016 à 19:44, Scott Kostyshak a écrit :
On Fri, Aug 12, 2016 at 07:28:57PM +0100, Guillaume Munch wrote:
Le 12/08/2016 à 01:23, Scott Kostyshak a écrit :
The change is due to 7ac70092. From what I understand, this is an
intended change and there's no easy way to make alt+x work the
On Fri, Aug 12, 2016 at 07:28:57PM +0100, Guillaume Munch wrote:
> Le 12/08/2016 à 01:23, Scott Kostyshak a écrit :
> >
> > The change is due to 7ac70092. From what I understand, this is an
> > intended change and there's no easy way to make alt+x work the second
> > time. I'll give up here on
Le 12/08/2016 à 01:23, Scott Kostyshak a écrit :
The change is due to 7ac70092. From what I understand, this is an
intended change and there's no easy way to make alt+x work the second
time. I'll give up here on this, unless someone gives me an idea for a
possible solution.
By looking at it,
On Tue, Jul 19, 2016 at 08:14:42PM -0400, Scott Kostyshak wrote:
> On Tue, Jul 19, 2016 at 10:57:11AM -0700, Pavel Sanda wrote:
> > Scott Kostyshak wrote:
> > > if I open the minibuffer, then click into the work area, and then
> > > execute alt+x, I expect the focus t
On Tue, Jul 19, 2016 at 10:57:11AM -0700, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > if I open the minibuffer, then click into the work area, and then
> > execute alt+x, I expect the focus to switch to the mini-buffer (just as
> > it does if the mini-buffer is not ope
Scott Kostyshak wrote:
> if I open the minibuffer, then click into the work area, and then
> execute alt+x, I expect the focus to switch to the mini-buffer (just as
> it does if the mini-buffer is not open). Is that a correct expectation?
this is definitely regression it works perfe
Le 19/07/2016 à 09:56, Scott Kostyshak a écrit :
if I open the minibuffer, then click into the work area, and then
execute alt+x, I expect the focus to switch to the mini-buffer (just as
it does if the mini-buffer is not open). Is that a correct expectation?
A similar case is the outline
if I open the minibuffer, then click into the work area, and then
execute alt+x, I expect the focus to switch to the mini-buffer (just as
it does if the mini-buffer is not open). Is that a correct expectation?
A similar case is the outline. If the outline is open, ctrl+alt+o still
shifts focus
Auto feature for minibuffer toolbar
If I do
1. alt + x
2. alt + x
3. alt + x
The first one opens the mini-buffer, the second switches back to the
work area, and the third does nothing. I expected the third to switch
back to the mini-buffer. Do I misunderstand how it is supposed to
work
Lasgouttes lasgout...@lyx.org
Date: Sat Apr 18 19:10:33 2015 +0200
Auto feature for minibuffer toolbar
If I do
1. alt + x
2. alt + x
3. alt + x
The first one opens the mini-buffer, the second switches back to the
work area, and the third does nothing. I expected the third
gt; Date: Sat Apr 18 19:10:33 2015 +0200
> >
> > Auto feature for minibuffer toolbar
>
> If I do
>
> 1. alt + x
> 2. alt + x
> 3. alt + x
>
> The first one opens the mini-buffer, the second switches back to the
> work area, and the third does nothing. I
17098afbe14
> > > Author: Jean-Marc Lasgouttes <lasgout...@lyx.org>
> > > Date: Sat Apr 18 19:10:33 2015 +0200
> > >
> > > Auto feature for minibuffer toolbar
> >
> > If I do
> >
> > 1. alt + x
> > 2. alt + x
>
Am Mittwoch, 15. Juli 2015 um 18:43:36, schrieb Kornel Benko kor...@lyx.org
Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 15/07/2015 15:26, Kornel Benko a écrit :
So, can I apply my patch now?
I have to fight with some tests, but YES.
Am 15.07.2015 um 19:07 schrieb Kornel Benko kor...@lyx.org:
Am Mittwoch, 15. Juli 2015 um 18:43:36, schrieb Kornel Benko kor...@lyx.org
Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 15/07/2015 15:26, Kornel Benko a écrit :
So, can I apply my
Am Mittwoch, 15. Juli 2015 um 20:37:35, schrieb Stephan Witt st.w...@gmx.net
Also I have now a reproducible crash, but only with my private user dir.
1.) Open a file
2.) try to insert space in the middle of a word == crash
This recipe doesn't work for me. Do you have an example file to
Toolbars
minibuffer on,bottom
End
===
This should just work, IMO.
With respect to 'minibuffer' I am with you.
So, can I apply my patch now?
JMarc
Am 15.07.2015 um 20:46 schrieb Kornel Benko kor...@lyx.org:
Am Mittwoch, 15. Juli 2015 um 20:37:35, schrieb Stephan Witt st.w...@gmx.net
Also I have now a reproducible crash, but only with my private user dir.
1.) Open a file
2.) try to insert space in the middle of a word == crash
Am Mittwoch, 15. Juli 2015 um 18:43:36, schrieb Kornel Benko kor...@lyx.org
Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 15/07/2015 15:26, Kornel Benko a écrit :
So, can I apply my patch now?
I have to fight with some tests, but YES.
On Wed, Jul 15, 2015 at 11:43 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
commit 7ac700920f0de8165b834010e211517098afbe14
Author: Jean-Marc Lasgouttes lasgout...@lyx.org
Date: Sat Apr 18 19:10:33 2015 +0200
Auto feature for minibuffer toolbar
If I do
1. alt + x
2. alt + x
3
or xxdefaults.ui that contains
===
Format 2
Include default.ui
Toolbars
minibuffer on,bottom
End
===
This should just work, IMO.
With respect to 'minibuffer' I am with you.
So, can I apply my patch now?
JMarc
I have
Le 15/07/2015 15:26, Kornel Benko a écrit :
So, can I apply my patch now?
I have to fight with some tests, but YES.
OK, I did it now. Have fun :)
JMarc
Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 15/07/2015 15:26, Kornel Benko a écrit :
So, can I apply my patch now?
I have to fight with some tests, but YES.
OK, I did it now. Have fun :)
JMarc
In trying to correct a test, I see now the
;default.ui"
Toolbars
"minibuffer" "on,bottom"
End
===
This should just work, IMO.
With respect to 'minibuffer' I am with you.
So, can I apply my patch now?
JMarc
02, Kornel Benko a écrit :
> >> Just create your test.ui or xxdefaults.ui that contains
> >>
> >> ===
> >> Format 2
> >>
> >> Include "default.ui"
> >>
> >>
> >> Toolbars
> >>"
Le 15/07/2015 15:26, Kornel Benko a écrit :
So, can I apply my patch now?
I have to fight with some tests, but YES.
OK, I did it now. Have fun :)
JMarc
Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
> Le 15/07/2015 15:26, Kornel Benko a écrit :
> >> So, can I apply my patch now?
> >
> > I have to fight with some tests, but YES.
>
> OK, I did it now. Have fun :)
>
> JMarc
In trying to correct a test,
Am Mittwoch, 15. Juli 2015 um 18:43:36, schrieb Kornel Benko
> Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
>
> > Le 15/07/2015 15:26, Kornel Benko a écrit :
> > >> So, can I apply my patch now?
> > >
> > > I have to fight with some
Am 15.07.2015 um 19:07 schrieb Kornel Benko :
> Am Mittwoch, 15. Juli 2015 um 18:43:36, schrieb Kornel Benko
>> Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
>>
>>> Le 15/07/2015 15:26, Kornel Benko a écrit :
> So,
Am Mittwoch, 15. Juli 2015 um 20:37:35, schrieb Stephan Witt
> >
> > Also I have now a reproducible crash, but only with my private user dir.
> >
> > 1.) Open a file
> > 2.) try to insert space in the middle of a word ==> crash
>
> This recipe doesn't work for me. Do you have an
Am 15.07.2015 um 20:46 schrieb Kornel Benko :
> Am Mittwoch, 15. Juli 2015 um 20:37:35, schrieb Stephan Witt
>>>
>>> Also I have now a reproducible crash, but only with my private user dir.
>>>
>>> 1.) Open a file
>>> 2.) try to insert space in the middle of a
On Wed, Jul 15, 2015 at 11:43 AM, Jean-Marc Lasgouttes
<lasgout...@lyx.org> wrote:
> commit 7ac700920f0de8165b834010e211517098afbe14
> Author: Jean-Marc Lasgouttes <lasgout...@lyx.org>
> Date: Sat Apr 18 19:10:33 2015 +0200
>
> Auto feature for minibuffer toolbar
Am Mittwoch, 15. Juli 2015 um 18:43:36, schrieb Kornel Benko
> Am Mittwoch, 15. Juli 2015 um 17:44:22, schrieb Jean-Marc Lasgouttes
>
> > Le 15/07/2015 15:26, Kornel Benko a écrit :
> > >> So, can I apply my patch now?
> > >
> > > I have to fight with some
Toolbars
minibuffer on,bottom
End
===
This should just work, IMO.
JMarc
Am Mittwoch, 1. Juli 2015 um 10:57:59, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 30/06/2015 11:32, Kornel Benko a écrit :
I'll think about it. You can also have a working environment where the
minibuffer toolbar is not auto but on. This supposedly works.
I could not find a way
Le 01/07/2015 11:34, Kornel Benko a écrit :
Thanks, after examining the patch, I already found it. But the lack of a
preference entry
makes it so un-handy.
We need something which could extend the default.ui.
Say it has the content
...
Toolbars
minibuffer auto,off,bottom
End
Toolbar
or xxdefaults.ui that contains
===
Format 2
Include default.ui
Toolbars
minibuffer on,bottom
End
===
This should just work, IMO.
With respect to 'minibuffer' I am with you.
The other probably deserves different subject
the default.ui.
Say it has the content
...
Toolbars
minibuffer auto,off,bottom
End
Toolbar extra Extra
Item Set language slovak language slovak
End
...
This would overwrite only the minibuffer entry in defaults.ui and add the
Item to the 'Extra' toolbar from
Am Mittwoch, 1. Juli 2015 um 10:57:59, schrieb Jean-Marc Lasgouttes
<lasgout...@lyx.org>
> Le 30/06/2015 11:32, Kornel Benko a écrit :
> >> I'll think about it. You can also have a working environment where the
> >> minibuffer toolbar is not auto but on. This suppos
Le 01/07/2015 11:34, Kornel Benko a écrit :
Thanks, after examining the patch, I already found it. But the lack of a
preference entry
makes it so un-handy.
We need something which could extend the default.ui.
Say it has the content
...
Toolbars
"minibuffer" "auto,
gt; We need something which could extend the default.ui.
> >
> > Say it has the content
> > ...
> > Toolbars
> > "minibuffer" "auto,off,bottom"
> > End
> > Toolbar "extra" "Extra"
> > Item "Set lang
lt.ui"
Toolbars
"minibuffer" "on,bottom"
End
===
This should just work, IMO.
JMarc
user ui file.
>
> Just create your test.ui or xxdefaults.ui that contains
>
> ===
> Format 2
>
> Include "default.ui"
>
>
> Toolbars
> "minibuffer" "on,bottom"
> End
> ===
>
>
Commit fdcff02a3124845d1033d3d804cede127850ff0f:
This commit has 2 view modes:
1.) auto with the new behaviour
2.) no displayed command minibuffer at all
The second mode is very inconvenient compared to the previous behaviour.
Could it be please changed Jean-Marc?
Kornel
the start'
Clocking on 'yes' or 'no' closes the minibuffer _and_ also the spellchecker
window.
This behaviour is not OK, since our key-tests cannot work anymore.
Wrong example. The file had no problems with spellchecking, the behaviour with
the dialog is the same as before.
The only difference
Commit fdcff02a3124845d1033d3d804cede127850ff0f:
This commit has 2 view modes:
1.) auto with the new behaviour
2.) no displayed command minibuffer at all
The second mode is very inconvenient compared to the previous behaviour.
Could it be please changed Jean-Marc?
Kornel
'
Clocking on 'yes' or 'no' closes the minibuffer _and_ also the spellchecker
window.
This behaviour is not OK, since our key-tests cannot work anymore.
Wrong example. The file had no problems with spellchecking, the behaviour with
the dialog is the same as before.
The only difference is the now
Am Montag, 22. Juni 2015 um 16:10:35, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 19/06/2015 16:31, Kornel Benko a écrit :
From memory:
1.) start lyx, the minibuffer is already displayed.
2.) open any file
3.) M-x, the cursor is displayed in the minibuffer
4.) M-x
Am Montag, 22. Juni 2015 um 16:53:06, schrieb Kornel Benko kor...@lyx.org
Am Montag, 22. Juni 2015 um 16:10:35, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 19/06/2015 16:31, Kornel Benko a écrit :
From memory:
1.) start lyx, the minibuffer is already displayed.
2.) open any
Le 19/06/2015 16:31, Kornel Benko a écrit :
From memory:
1.) start lyx, the minibuffer is already displayed.
2.) open any file
3.) M-x, the cursor is displayed in the minibuffer
4.) M-x, in the minibuffer appears 'x'
5.) click on a view, cursor is displayed in both, minibuffer and buffer
6
Le 19/06/2015 16:31, Kornel Benko a écrit :
From memory:
1.) start lyx, the minibuffer is already displayed.
2.) open any file
3.) M-x, the cursor is displayed in the minibuffer
4.) M-x, in the minibuffer appears 'x'
5.) click on a view, cursor is displayed in both, minibuffer and buffer
6
Am Montag, 22. Juni 2015 um 16:10:35, schrieb Jean-Marc Lasgouttes
<lasgout...@lyx.org>
> Le 19/06/2015 16:31, Kornel Benko a écrit :
> > From memory:
> > 1.) start lyx, the minibuffer is already displayed.
> > 2.) open any file
> > 3.) M-x, the cursor is displa
Am Montag, 22. Juni 2015 um 16:53:06, schrieb Kornel Benko <kor...@lyx.org>
> Am Montag, 22. Juni 2015 um 16:10:35, schrieb Jean-Marc Lasgouttes
> <lasgout...@lyx.org>
> > Le 19/06/2015 16:31, Kornel Benko a écrit :
> > > From memory:
> > > 1.) star
Le 18/06/2015 17:41, Kornel Benko a écrit :
With this patch every key is going to the minibuffer. I tried cua and emacs
binding.
Could you give more details on what you do?
JMarc
Am Freitag, 19. Juni 2015 um 16:12:17, schrieb Jean-Marc Lasgouttes
lasgout...@lyx.org
Le 18/06/2015 17:41, Kornel Benko a écrit :
With this patch every key is going to the minibuffer. I tried cua and emacs
binding.
Could you give more details on what you do?
JMarc
From memory:
1
Le 18/06/2015 17:41, Kornel Benko a écrit :
With this patch every key is going to the minibuffer. I tried cua and emacs
binding.
Could you give more details on what you do?
JMarc
Am Freitag, 19. Juni 2015 um 16:12:17, schrieb Jean-Marc Lasgouttes
<lasgout...@lyx.org>
> Le 18/06/2015 17:41, Kornel Benko a écrit :
> > With this patch every key is going to the minibuffer. I tried cua and emacs
> > binding.
>
> Could you give more details on wh
With this patch every key is going to the minibuffer. I tried cua and emacs
binding.
Kornel
signature.asc
Description: This is a digitally signed message part.
...@lyx.org
Date: Sat, 18 Apr 2015 19:10:33 +0200
Subject: [PATCH] Auto feature for minibuffer toolbar
Now the minibuffer toolbar is auto by default. It is opened by
command-execute (M-x) and closed when the command is executed.
---
lib/ui/default.ui | 2 +-
src/frontends/qt4
Am Donnerstag, 18. Juni 2015 um 08:38:28, schrieb Enrico Forestieri
for...@lyx.org
On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
What do you mean? For me M-x does not toggle, it just opens the
mini-buffer. Actually I just tested and if I press it rapidly many times
On Thu, Jun 18, 2015 at 08:51:12AM +0200, Kornel Benko wrote:
Am Donnerstag, 18. Juni 2015 um 08:38:28, schrieb Enrico Forestieri
for...@lyx.org
On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
What do you mean? For me M-x does not toggle, it just opens the
On Wed, Jun 17, 2015 at 05:51:28PM +0200, Jean-Marc Lasgouttes wrote:
Le 14/06/2015 07:48, Scott Kostyshak a écrit :
Note though that I do like that if I just press return (that is,
entering an empty string), the command buffer closes. The only reason
I like this though is that a subsequent
On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
What do you mean? For me M-x does not toggle, it just opens the
mini-buffer. Actually I just tested and if I press it rapidly many times
sometimes I can get it to close the mini-buffer. Yours toggles
perfectly? I wonder if this
On Thu, Jun 18, 2015 at 03:11:25AM -0400, Scott Kostyshak wrote:
On Thu, Jun 18, 2015 at 08:51:12AM +0200, Kornel Benko wrote:
Am Donnerstag, 18. Juni 2015 um 08:38:28, schrieb Enrico Forestieri
for...@lyx.org
On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
What
On Wed, Jun 17, 2015 at 05:51:28PM +0200, Jean-Marc Lasgouttes wrote:
> Le 14/06/2015 07:48, Scott Kostyshak a écrit :
> >>Note though that I do like that if I just press return (that is,
> >>entering an empty string), the command buffer closes. The only reason
> >>I like this though is that a
On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
>
> What do you mean? For me M-x does not toggle, it just opens the
> mini-buffer. Actually I just tested and if I press it rapidly many times
> sometimes I can get it to close the mini-buffer. Yours toggles
> perfectly? I wonder if
Am Donnerstag, 18. Juni 2015 um 08:38:28, schrieb Enrico Forestieri
> On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
> >
> > What do you mean? For me M-x does not toggle, it just opens the
> > mini-buffer. Actually I just tested and if I press it rapidly many
On Thu, Jun 18, 2015 at 08:51:12AM +0200, Kornel Benko wrote:
> Am Donnerstag, 18. Juni 2015 um 08:38:28, schrieb Enrico Forestieri
>
> > On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
> > >
> > > What do you mean? For me M-x does not toggle, it just opens the
On Thu, Jun 18, 2015 at 03:11:25AM -0400, Scott Kostyshak wrote:
> On Thu, Jun 18, 2015 at 08:51:12AM +0200, Kornel Benko wrote:
> > Am Donnerstag, 18. Juni 2015 um 08:38:28, schrieb Enrico Forestieri
> >
> > > On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
> >
arc Lasgouttes <lasgout...@lyx.org>
Date: Sat, 18 Apr 2015 19:10:33 +0200
Subject: [PATCH] Auto feature for minibuffer toolbar
Now the minibuffer toolbar is "auto" by default. It is opened by
command-execute (M-x) and closed when the command is executed.
---
lib/ui/default.ui
complain if I remove this
> "alt-x to close" feature?
>
> Here is a new patch updated to latest master changes.
>
> JMarc
With this patch every key is going to the minibuffer. I tried cua and emacs
binding.
Kornel
signature.asc
Description: This is a digitally signed message part.
Le 14/06/2015 07:48, Scott Kostyshak a écrit :
Note though that I do like that if I just press return (that is,
entering an empty string), the command buffer closes. The only reason
I like this though is that a subsequent alt + x does not hide the
mini-buffer.
I am not sure that I follow you
Le 14/06/2015 07:48, Scott Kostyshak a écrit :
Note though that I do like that if I just press return (that is,
entering an empty string), the command buffer closes. The only reason
I like this though is that a subsequent alt + x does not hide the
mini-buffer.
I am not sure that I follow you
On Tue, Apr 21, 2015 at 03:57:22PM -0400, Scott Kostyshak wrote:
On Mon, Apr 20, 2015 at 8:33 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
Also, what if you misspelled the command you entered so that the
command is disabled? Should the mini-buffer stay open so you can
correct it
On Tue, Apr 21, 2015 at 03:57:22PM -0400, Scott Kostyshak wrote:
> On Mon, Apr 20, 2015 at 8:33 AM, Jean-Marc Lasgouttes
> wrote:
>
> >> Also, what if you misspelled the command you entered so that the
> >> command is disabled? Should the mini-buffer stay open so you can
> >>
On Mon, Apr 20, 2015 at 8:33 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
Also, what if you misspelled the command you entered so that the
command is disabled? Should the mini-buffer stay open so you can
correct it quickly and enter it (without having to open the
mini-buffer again)? I
On Mon, Apr 20, 2015 at 8:33 AM, Jean-Marc Lasgouttes
wrote:
>> Also, what if you misspelled the command you entered so that the
>> command is disabled? Should the mini-buffer stay open so you can
>> correct it quickly and enter it (without having to open the
>> mini-buffer
Le 19/04/2015 00:00, Scott Kostyshak a écrit :
Regarding your comment
No need to keep the minibuffer open anymore
can you add why to the comment? Is it because a command was just executed?
Yes, exactly.
Also, what if you misspelled the command you entered so that the
command is disabled
Le 19/04/2015 00:00, Scott Kostyshak a écrit :
Regarding your comment
"No need to keep the minibuffer open anymore"
can you add why to the comment? Is it because a command was just executed?
Yes, exactly.
Also, what if you misspelled the command you entered so that the
command i
This patch makes minibuffer work like it does in emacs: it is open when
invoking M-x, and gets closed when the command has been executed.
It may be necessary to remove you session data (.config/LyX/lyx.conf for
linux) so that the toolbar gets the proper flags. This is probably a
problem when
On Sat, Apr 18, 2015 at 1:18 PM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
This patch makes minibuffer work like it does in emacs: it is open when
invoking M-x, and gets closed when the command has been executed.
It may be necessary to remove you session data (.config/LyX/lyx.conf
This patch makes minibuffer work like it does in emacs: it is open when
invoking M-x, and gets closed when the command has been executed.
It may be necessary to remove you session data (.config/LyX/lyx.conf for
linux) so that the toolbar gets the proper flags. This is probably a
problem when
On Sat, Apr 18, 2015 at 1:18 PM, Jean-Marc Lasgouttes
<lasgout...@lyx.org> wrote:
> This patch makes minibuffer work like it does in emacs: it is open when
> invoking M-x, and gets closed when the command has been executed.
>
> It may be necessary to remove you session data (.c
Vincent, Juergen,
is it ok with you to backport http://www.lyx.org/trac/changeset/28250
into 1.6.3?
pavel
Vincent, Juergen,
is it ok with you to backport http://www.lyx.org/trac/changeset/28250
into 1.6.3?
Ah, you like it!...
I still want to add another few thingies:
1. You're now able to choose a certain command with the mouse, but you
still have to press enter on the keyboard to execute it. I
Vincent van Ravesteijn - TNW wrote:
Vincent, Juergen,
is it ok with you to backport http://www.lyx.org/trac/changeset/28250
into 1.6.3?
Ah, you like it!...
i found it the harder way when loosing elaborted command after unwanted
lyx closing... 10mins lost ;)
I still want to add
Pavel Sanda wrote:
Juergen?
I need to have a closer look, but let us first finish 1.6.2, please.
Jürgen
Vincent, Juergen,
is it ok with you to backport http://www.lyx.org/trac/changeset/28250
into 1.6.3?
pavel
>Vincent, Juergen,
>
>is it ok with you to backport http://www.lyx.org/trac/changeset/28250
>into 1.6.3?
Ah, you like it!...
I still want to add another few thingies:
1. You're now able to choose a certain command with the mouse, but you
still have to press enter on the keyboard to execute
Vincent van Ravesteijn - TNW wrote:
>
> >Vincent, Juergen,
> >
> >is it ok with you to backport http://www.lyx.org/trac/changeset/28250
> >into 1.6.3?
>
> Ah, you like it!...
i found it the harder way when loosing elaborted command after unwanted
lyx closing... 10mins lost ;)
> I still want
Pavel Sanda wrote:
> Juergen?
I need to have a closer look, but let us first finish 1.6.2, please.
Jürgen
Martin Vermeer [EMAIL PROTECTED] writes:
Is there some place where I can read about the new state to the inset
world, btw?
Ah, you mean, like, documentation?
I thought about a wiki page for developers explaining how the
different insets fit together, but documentation is nice too.
JMarc
Martin Vermeer <[EMAIL PROTECTED]> writes:
>> Is there some place where I can read about the new state to the inset
>> world, btw?
>
> Ah, you mean, like, "documentation"?
I thought about a wiki page for developers explaining how the
different insets fit together, but documentation is nice too.
It turns out to be possible to exter in the minibuffer
a command: flex-insert Note:Comment, which will enter a
flex inset under the name Note:Comment, which looks,
feels and probably behaves like the real thing... only,
it's a flex inset.
I don't think we want this. The attached blocks
Martin Vermeer [EMAIL PROTECTED] writes:
It turns out to be possible to exter in the minibuffer
a command: flex-insert Note:Comment, which will enter a
flex inset under the name Note:Comment, which looks,
feels and probably behaves like the real thing... only,
it's a flex inset
On Sat, Sep 08, 2007 at 10:34:21AM +0200, Jean-Marc Lasgouttes wrote:
Martin Vermeer [EMAIL PROTECTED] writes:
It turns out to be possible to exter in the minibuffer
a command: flex-insert Note:Comment, which will enter a
flex inset under the name Note:Comment, which looks,
feels
1 - 100 of 493 matches
Mail list logo