On Wed, Jul 26, 2000 at 08:29:40AM +0200, Lars Gullik Bjønnes wrote:
> "R. Lahaye" <[EMAIL PROTECTED]> writes:
>
> | "Lars Gullik Bjønnes" wrote:
> | > Yes, the two second learning curve can be pretty hard.
> | > (what is nicest "Ctrl-x Ctrl-f" or "C-x C-f"?)
> |
> | I'm rather addressing "Why i
On Wed, 26 Jul 2000, R. Lahaye wrote:
> "Lars Gullik Bjønnes" wrote:
> > Yes, the two second learning curve can be pretty hard.
> > (what is nicest "Ctrl-x Ctrl-f" or "C-x C-f"?)
>
> I'm rather addressing "Why is it "M", when all keyboards
> I've seen in my entire life say "Alt"?
'M' stands for
"R. Lahaye" <[EMAIL PROTECTED]> writes:
| "Lars Gullik Bjønnes" wrote:
| > Yes, the two second learning curve can be pretty hard.
| > (what is nicest "Ctrl-x Ctrl-f" or "C-x C-f"?)
|
| I'm rather addressing "Why is it "M", when all keyboards
| I've seen in my entire life say "Alt"? And then why
"Lars Gullik Bjønnes" wrote:
> Yes, the two second learning curve can be pretty hard.
> (what is nicest "Ctrl-x Ctrl-f" or "C-x C-f"?)
I'm rather addressing "Why is it "M", when all keyboards
I've seen in my entire life say "Alt"? And then why not
use "Shift" and "Ctrl" as well. In a variable wid
"R. Lahaye" <[EMAIL PROTECTED]> writes:
|_New... C-n
|
| Where does the "C-n" come from? Is that silently added to
| the entry? Is there a way to remove it and/or change it?
The C-n is the command shortcut. for you probably defined in cua.bind.
| Something different: LyX menus (and the d
Jean-Marc Lasgouttes wrote:
> Menuset
>
> Menubar "main"
> Submenu "File|F" "file"
> Submenu "Edit|E" "edit"
[...]
> Menu "file"
> Item "New...|N" "buffer-new"
[snip]
This File->New menu item, for example, looks on my
screen as ("_N" is an "underlined N"):
_N
On Tue, Jul 25, 2000 at 01:48:00PM +0100, Jose Abilio Oliveira Matos wrote:
> On Tue, Jul 25, 2000 at 02:25:52PM +0200, Jean-Marc Lasgouttes wrote:
> [...]
> > BTW, Jose', why is it necessary to have three different html export
> > types? I' think the "export html" function could be clever enough
Allan Rae <[EMAIL PROTECTED]> writes:
| Then leave them out of the menu. It's likely to be a week before I get
| around to removing the other ones anyway. And 1.1.6 is probably going to
| be out before then.
1.1.6 in a week? Are you kidding? We need to have at least one
prerelease first...
On 25 Jul 2000, Jean-Marc Lasgouttes wrote:
> > "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
>
> Allan> Ahh. I misunderstood your cvslog posting. Those are currently
> Allan> called directly from within the menu code (Menu?? callback) so
> Allan> I guess you should add a lyxfunc for them
> "Jose" == Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
Jose> On Tue, Jul 25, 2000 at 01:48:00PM +0100, Jose Abilio Oliveira
Jose> Matos wrote:
>> The other choice is you to do it.;)
>>
Jose> I have been unable to update the cvs code. The connection is
Jose> extremely slow. And
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> Ahh. I misunderstood your cvslog posting. Those are currently
Allan> called directly from within the menu code (Menu?? callback) so
Allan> I guess you should add a lyxfunc for them that simply calls
Allan> whatever function in lyx_cb.C
> Hmmm, to me this looks like every entry is designed as a sort of
> failsafe:
> if you hit the wrong entry you still can do what you wanted to do.
These properties of the commands are good. We should not remove these.
Let me explain why.
Yes, it's possible to create a new document with the "Op
> "Jose" == Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
Jose> If I patch that what are the place that I should change? That
Jose> is, what are the places where you have used it.
What you have to change is MenuExport() (of course), but also the
conditional code in LyXFunc::getSta
On Tue, Jul 25, 2000 at 01:48:00PM +0100, Jose Abilio Oliveira Matos wrote:
>
> The other choice is you to do it.;)
>
I have been unable to update the cvs code. The connection
is extremely slow. And it breaks during the update stage.
--
José
On 25 Jul 2000, Jean-Marc Lasgouttes wrote:
> Juergen> MenuItem(): LyX command `screen-options' does not exist.
> Juergen> MenuItem(): LyX command `spellchecker-options' does not
> Juergen> exist. MenuItem(): LyX command `keyboard-options' does not
> Juergen> exist.
> Juergen> MenuItem(): LyX comm
On Tue, Jul 25, 2000 at 02:25:52PM +0200, Jean-Marc Lasgouttes wrote:
[...]
> BTW, Jose', why is it necessary to have three different html export
> types? I' think the "export html" function could be clever enough to
> do the right thing...
You are right, since I have the buffer I can simply d
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> MenuItem(): LyX command `external-inset-insert' does not
Juergen> exist.
Fixed.
Juergen> MenuItem(): LyX command `screen-options' does not exist.
Juergen> MenuItem(): LyX command `spellchecker-options' does not
Juergen> exist
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
>> With the new OptItem scheme I will commit soon, it will be easy to
>> add All the locking inset menu entries in the menu, and only the
>> one which makes sense will be shown. Does it sound good to you?
>>
Juergen> How is this supp
>
> ERROR:create_submenu: Unknown menu `floats'
> Error in MenuCallback
>
I get also:
MenuItem(): LyX command `external-inset-insert' does not exist.
MenuItem(): LyX command `screen-options' does not exist.
MenuItem(): LyX command `spellchecker-options' does not exist.
MenuItem(): LyX command
>
> With the new OptItem scheme I will commit soon, it will be easy to add
> All the locking inset menu entries in the menu, and only the one which
> makes sense will be shown. Does it sound good to you?
>
How is this supposed to work? I would only need 1 entry for accessing an
eventually exist
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> I would insert here (inseted of TabularLayout) something like
Juergen> TheLockingInset (find a better name but that is
Juergen> what it shoud do)
Juergen> we then need a function in the insets which tells us if
Juer
On 24-Jul-2000 Lars Gullik Bjønnes wrote:
>
> I don't agree. And you _have_ managd with a popuå on both items in
> several years now.
>
So why not extend this with 5 other popups so we just have a little more
options to select from when creating just a dummy document to try new stuff!
Jü
"R. Lahaye" wrote:
> File->New // Collapse New and New_from_template.
> // Use "invalid" filename; when saved, call 'Save as...' automatically.
> // Should a window popup ask for Template/Class or assume a default for
>that?
> Open // Collapse Open and Import. Open accor
Juergen Vigna <[EMAIL PROTECTED]> writes:
| > File->New // Collapse New and New_from_template.
| > // Use "invalid" filename; when saved, call 'Save as...' automatically.
| > // Should a window popup ask for Template/Class or assume a default for
|that?
|
| NO, NO, NO!
|
>
>
> File->New // Collapse New and New_from_template.
> // Use "invalid" filename; when saved, call 'Save as...' automatically.
> // Should a window popup ask for Template/Class or assume a default for
>that?
NO, NO, NO!
IMO we need "New..." AND "New from template..."
> "Rob" == R Lahaye <[EMAIL PROTECTED]> writes:
Rob> That's wonderful news! But what have you appended? Can't find it?
Rob> Or do I need to grab it from CVS?
As you have noticed, I forgot it :) Here is it now. This will go in
cvs tomorrow.
Rob> However, a LyX release will always have to co
Jean-Marc Lasgouttes wrote:
> Therefore, you will be able to change it on-the-fly. I append for
> reference the menu I have currently, which should be self-explaining.
> You might want to use this syntax for your new scheme.
That's wonderful news! But what have you appended? Can't find it?
Or do
> "Rob" == R Lahaye <[EMAIL PROTECTED]> writes:
Rob> Hi, I've started the "Cleaning up the menu entries" issue and
Rob> according to the wishes/comments/explanations in the thread I
Rob> have composed a new menu layout.
Rob> Where entries have changed (name and/or action) I've added
Rob> add
28 matches
Mail list logo
