On Fri, Dec 13, 2002 at 03:37:26PM +1000, Allan Rae wrote:
$VISUAL is supposed to be the name of a $EDITOR that doesn't require a
terminal. Save some pain and just use $VISUAL instead of $EDITOR to
invoke your editor.
Ah. I did not know that. Maybe because I rarely use editors that don't need
On Fri, Dec 13, 2002 at 03:37:26PM +1000, Allan Rae wrote:
> $VISUAL is supposed to be the name of a $EDITOR that doesn't require a
> terminal. Save some pain and just use $VISUAL instead of $EDITOR to
> invoke your editor.
Ah. I did not know that. Maybe because I rarely use editors that don't
On Tue, 10 Dec 2002, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 08:35:53AM +0100, Alfredo Braunstein wrote:
The preference of an external editor should be stated by setting the
EDITOR environment variale to an appropriate value. No need to re-invent
the wheel...
That's how it's
On Tue, 10 Dec 2002, Andre Poenitz wrote:
> On Tue, Dec 10, 2002 at 08:35:53AM +0100, Alfredo Braunstein wrote:
> > > The preference of an external editor should be stated by setting the
> > > EDITOR environment variale to an appropriate value. No need to re-invent
> > > the wheel...
> >
> >
John == John Levon [EMAIL PROTECTED] writes:
John On Tue, Dec 10, 2002 at 12:23:24PM +0100, Jean-Marc Lasgouttes
John wrote:
Another solution: add a method GUIruntime::isImplemented(kb_action)
that would return false for not implemented actions. Then these
would be ignored by MenuBackend. The
On Wed, Dec 11, 2002 at 10:38:23AM +0100, Jean-Marc Lasgouttes wrote:
John And you're going to ignore the Separator below Tooltips how ?
I'm sure that your menu frontend code ignores separators at the top or
bottom of menus, doesn't it?
I doubt it :)
But if it must, it will still
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Tue, Dec 10, 2002 at 12:23:24PM +0100, Jean-Marc Lasgouttes
John> wrote:
>> Another solution: add a method GUIruntime::isImplemented(kb_action)
>> that would return false for not implemented actions. Then these
>> would be ignored by
On Wed, Dec 11, 2002 at 10:38:23AM +0100, Jean-Marc Lasgouttes wrote:
> John> And you're going to ignore the Separator below Tooltips how ?
>
> I'm sure that your menu frontend code ignores separators at the top or
> bottom of menus, doesn't it?
I doubt it :)
But if it must, it will still
John == John Levon [EMAIL PROTECTED] writes:
John On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein
John wrote:
1) first patch to enable Layout-Preamble
John I don't think we want this. Preamble has been moved to the
John Document dialog. We need to make the menus frontend-specific
Jean-Marc Lasgouttes wrote:
What about the idea of disabling preamble if it is not hooked to a
signal? I can do that if someone tells me how I can test for this
condition.
What about the optitem (related to frontend) idea? Then you can disable
tooltips and child processes too, and I'm shure
Juergen Spitzmueller wrote:
tooltip specific issues
frontend specific issues...
Jürgen.
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:
Juergen Jean-Marc Lasgouttes wrote:
What about the idea of disabling preamble if it is not hooked to a
signal? I can do that if someone tells me how I can test for this
condition.
Juergen What about the optitem (related to frontend)
On Tuesday 10 December 2002 8:45 am, Jean-Marc Lasgouttes wrote:
John == John Levon [EMAIL PROTECTED] writes:
John On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein
John wrote:
1) first patch to enable Layout-Preamble
John I don't think we want this. Preamble has been moved to
On Mon Dec 9, 2002 21:04, Alfredo Braunstein wrote:
Hi,
1) first patch to enable Layout-Preamble
2) second patch: to
a) eliminate a crash on Layout-Preamble-Edit-Cancel (a NULL
point er was assigned to a string)
b) adds 'xterm -e ' when calling the editor from $EDITOR
Hope
On Tue Dec 10, 2002 10:16, Edwin Leuven wrote:
On Mon Dec 9, 2002 21:04, Alfredo Braunstein wrote:
Hi,
1) first patch to enable Layout-Preamble
2) second patch: to
a) eliminate a crash on Layout-Preamble-Edit-Cancel (a NULL
point er was assigned to a string)
b) adds
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Jean-Marc, none of them are hooked to signals anymore. See
Angus xforms/Dialogs_impl.h, xforms/Dialogs2.C.
OK, I see.
Angus What we could do is have all these methods return a bool
Angus telling the core whether the request has been dealt
On Tuesday 10 December 2002 10:06 am, Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Jean-Marc, none of them are hooked to signals anymore. See
Angus xforms/Dialogs_impl.h, xforms/Dialogs2.C.
OK, I see.
Angus What we could do is have all these methods
On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
Well then, I see no alternative but to write a bunch of 1-line functions for
each frontend (below). If they default to true, then you'll have to overload
only a few in the respective frontends...
frontends/Dialogs.h
class
On Tuesday 10 December 2002 10:21 am, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
Well then, I see no alternative but to write a bunch of 1-line functions
for each frontend (below). If they default to true, then you'll have to
overload only a few in
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus On Tuesday 10 December 2002 10:21 am, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
Well then, I see no alternative but to write a bunch of 1-line
functions for each frontend (below). If they
On Tuesday 10 December 2002 10:47 am, Jean-Marc Lasgouttes wrote:
Angus Excellent idea. It's a major pain that adding a new dialog
Angus causes the re-compilation of the whole LyX tree.
In this case, we should also have showDialog(string const name) and
a map name-dialog of some sort.
On Tue, Dec 10, 2002 at 11:09:35AM +, Angus Leeming wrote:
No. I reckon that for 1.3 you should go for the simple to code multiple
virtual bool haveXYZ() { return true; }
and overload the few cases in Qt where they decided that they don't want a
dialog.
Wouldn't it even for 1.3 be
Edwin Leuven [EMAIL PROTECTED] writes:
| redundant now (preamble is in document settings dialog). I also think the
| show preamble entry should be removed from the (qt) menu.
Or just make the QDocument::preamble pop up...
--
Lgb
On Tuesday 10 December 2002 11:10 am, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 11:09:35AM +, Angus Leeming wrote:
No. I reckon that for 1.3 you should go for the simple to code multiple
virtual bool haveXYZ() { return true; }
and overload the few cases in Qt where they decided
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Edwin Leuven [EMAIL PROTECTED] writes: | redundant now
Lars (preamble is in document settings dialog). I also think the |
Lars show preamble entry should be removed from the (qt) menu.
Lars Or just make the QDocument::preamble pop up...
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars Edwin Leuven [EMAIL PROTECTED] writes: | redundant now
| Lars (preamble is in document settings dialog). I also think the |
| Lars show preamble entry should be removed from the (qt)
On Tue, Dec 10, 2002 at 11:28:56AM +, Angus Leeming wrote:
Wouldn't it even for 1.3 be simpler to have the 'name' argument and an 'if'
cascade in the Qt implementation?
Whatever. It should needs implementing SOMEHOW. Two minutes to code. 10
minutes to compile on a fast machine (*). 1
On Tue, Dec 10, 2002 at 12:23:24PM +0100, Jean-Marc Lasgouttes wrote:
Another solution: add a method GUIruntime::isImplemented(kb_action)
that would return false for not implemented actions. Then these would
be ignored by MenuBackend. The advantage is simplicity, and
possibility to ignore
Edwin Leuven wrote:
And after sending this I contniued to read the thread: sorry (guess I am
still asleep).
Ed.
Don't worry... For sure you were not the only one... Thanks¸ Alfredo
John Levon wrote:
On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein wrote:
1) first patch to enable Layout-Preamble
I don't think we want this. Preamble has been moved to the Document
dialog. We need to make the menus frontend-specific to remove the menu
Ah, I knew I was
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein
John> wrote:
>> 1) first patch to enable Layout->Preamble
John> I don't think we want this. Preamble has been moved to the
John> Document dialog. We need to make the menus
Jean-Marc Lasgouttes wrote:
> What about the idea of disabling preamble if it is not hooked to a
> signal? I can do that if someone tells me how I can test for this
> condition.
What about the optitem (related to frontend) idea? Then you can disable
tooltips and child processes too, and I'm
Juergen Spitzmueller wrote:
> tooltip specific issues
frontend specific issues...
Jürgen.
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> What about the idea of disabling preamble if it is not hooked to a
>> signal? I can do that if someone tells me how I can test for this
>> condition.
Juergen> What about the optitem
On Tuesday 10 December 2002 8:45 am, Jean-Marc Lasgouttes wrote:
> > "John" == John Levon <[EMAIL PROTECTED]> writes:
>
> John> On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein
>
> John> wrote:
> >> 1) first patch to enable Layout->Preamble
>
> John> I don't think we want this.
On Mon Dec 9, 2002 21:04, Alfredo Braunstein wrote:
> Hi,
>
> 1) first patch to enable Layout->Preamble
> 2) second patch: to
> a) eliminate a crash on Layout->Preamble->Edit->Cancel (a NULL
> point er was assigned to a string)
> b) adds 'xterm -e ' when calling the editor from
On Tue Dec 10, 2002 10:16, Edwin Leuven wrote:
> On Mon Dec 9, 2002 21:04, Alfredo Braunstein wrote:
> > Hi,
> >
> > 1) first patch to enable Layout->Preamble
> > 2) second patch: to
> > a) eliminate a crash on Layout->Preamble->Edit->Cancel (a NULL
> > point er was assigned to a string)
>
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc, none of them are hooked to signals anymore. See
Angus> xforms/Dialogs_impl.h, xforms/Dialogs2.C.
OK, I see.
Angus> What we could do is have all these methods return a bool
Angus> telling the core whether the request
On Tuesday 10 December 2002 10:06 am, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Jean-Marc, none of them are hooked to signals anymore. See
> Angus> xforms/Dialogs_impl.h, xforms/Dialogs2.C.
>
> OK, I see.
>
> Angus> What we could do is have
On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
> Well then, I see no alternative but to write a bunch of 1-line functions for
> each frontend (below). If they default to true, then you'll have to overload
> only a few in the respective frontends...
>
> frontends/Dialogs.h
>
>
On Tuesday 10 December 2002 10:21 am, Andre Poenitz wrote:
> On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
> > Well then, I see no alternative but to write a bunch of 1-line functions
> > for each frontend (below). If they default to true, then you'll have to
> > overload only a
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> On Tuesday 10 December 2002 10:21 am, Andre Poenitz wrote:
>> On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote: >
>> Well then, I see no alternative but to write a bunch of 1-line
>> functions > for each frontend
On Tuesday 10 December 2002 10:47 am, Jean-Marc Lasgouttes wrote:
> Angus> Excellent idea. It's a major pain that adding a new dialog
> Angus> causes the re-compilation of the whole LyX tree.
>
> In this case, we should also have showDialog(string const & name) and
> a map name->dialog of some
On Tue, Dec 10, 2002 at 11:09:35AM +, Angus Leeming wrote:
> No. I reckon that for 1.3 you should go for the simple to code multiple
> virtual bool haveXYZ() { return true; }
> and overload the few cases in Qt where they decided that they don't want a
> dialog.
Wouldn't it even for 1.3
Edwin Leuven <[EMAIL PROTECTED]> writes:
| redundant now (preamble is in document settings dialog). I also think the
| show preamble entry should be removed from the (qt) menu.
Or just make the QDocument::preamble pop up...
--
Lgb
On Tuesday 10 December 2002 11:10 am, Andre Poenitz wrote:
> On Tue, Dec 10, 2002 at 11:09:35AM +, Angus Leeming wrote:
> > No. I reckon that for 1.3 you should go for the simple to code multiple
> > virtual bool haveXYZ() { return true; }
> > and overload the few cases in Qt where they
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Edwin Leuven <[EMAIL PROTECTED]> writes: | redundant now
Lars> (preamble is in document settings dialog). I also think the |
Lars> show preamble entry should be removed from the (qt) menu.
Lars> Or just make the
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Edwin Leuven <[EMAIL PROTECTED]> writes: | redundant now
| Lars> (preamble is in document settings dialog). I also think the |
| Lars> show preamble entry should be
On Tue, Dec 10, 2002 at 11:28:56AM +, Angus Leeming wrote:
> > Wouldn't it even for 1.3 be simpler to have the 'name' argument and an 'if'
> > cascade in the Qt implementation?
>
> Whatever. It should needs implementing SOMEHOW. Two minutes to code. 10
> minutes to compile on a fast machine
On Tue, Dec 10, 2002 at 12:23:24PM +0100, Jean-Marc Lasgouttes wrote:
> Another solution: add a method GUIruntime::isImplemented(kb_action)
> that would return false for not implemented actions. Then these would
> be ignored by MenuBackend. The advantage is simplicity, and
> possibility to ignore
Edwin Leuven wrote:
> And after sending this I contniued to read the thread: sorry (guess I am
> still asleep).
>
> Ed.
Don't worry... For sure you were not the only one... Thanks¸ Alfredo
John Levon wrote:
> On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein wrote:
>
>> 1) first patch to enable Layout->Preamble
>
> I don't think we want this. Preamble has been moved to the Document
> dialog. We need to make the menus frontend-specific to remove the menu
Ah, I knew I
Hi,
1) first patch to enable Layout-Preamble
2) second patch: to
a) eliminate a crash on Layout-Preamble-Edit-Cancel (a NULL point
er was assigned to a string)
b) adds 'xterm -e ' when calling the editor from $EDITOR
Hope it's of some use, Alfredo
Index: Dialogs2.C
Alfredo Braunstein [EMAIL PROTECTED] writes:
| 1) first patch to enable Layout-Preamble
The qt people must look at this one.
| 2) second patch: to
| a) eliminate a crash on Layout-Preamble-Edit-Cancel (a NULL point
| er was assigned to a string)
Ok, I guess. But some more spaces
Lars Gullik Bjønnes wrote:
| b) adds 'xterm -e ' when calling the editor from $EDITOR
I am not so sure about this one... what if my $EDITOR is emacsclient?
An xterm will flash for a second and the editor will be launched correctly I
guess (?). Isn't it better than the present
On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein wrote:
1) first patch to enable Layout-Preamble
I don't think we want this. Preamble has been moved to the Document
dialog. We need to make the menus frontend-specific to remove the menu
item (and others like Help-Tooltips). But
On Mon, Dec 09, 2002 at 11:27:30PM +0100, Alfredo Braunstein wrote:
It looks broken anyway. Maybe it's better to call an external editor
configurable by preferences?
The preference of an external editor should be stated by setting the EDITOR
environment variale to an appropriate value. No need
Andre Poenitz wrote:
On Mon, Dec 09, 2002 at 11:27:30PM +0100, Alfredo Braunstein wrote:
It looks broken anyway. Maybe it's better to call an external editor
configurable by preferences?
The preference of an external editor should be stated by setting the
EDITOR environment variale to an
On Tue, Dec 10, 2002 at 08:35:53AM +0100, Alfredo Braunstein wrote:
The preference of an external editor should be stated by setting the
EDITOR environment variale to an appropriate value. No need to re-invent
the wheel...
That's how it's implemented right now. The problem is that we
Hi,
1) first patch to enable Layout->Preamble
2) second patch: to
a) eliminate a crash on Layout->Preamble->Edit->Cancel (a NULL point
er was assigned to a string)
b) adds 'xterm -e ' when calling the editor from $EDITOR
Hope it's of some use, Alfredo
Index: Dialogs2.C
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| 1) first patch to enable Layout->Preamble
The qt people must look at this one.
| 2) second patch: to
| a) eliminate a crash on Layout->Preamble->Edit->Cancel (a NULL point
| er was assigned to a string)
Ok, I guess. But some more spaces
Lars Gullik Bjønnes wrote:
> | b) adds 'xterm -e ' when calling the editor from $EDITOR
>
> I am not so sure about this one... what if my $EDITOR is "emacsclient"?
>
An xterm will flash for a second and the editor will be launched correctly I
guess (?). Isn't it better than the
On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein wrote:
> 1) first patch to enable Layout->Preamble
I don't think we want this. Preamble has been moved to the Document
dialog. We need to make the menus frontend-specific to remove the menu
item (and others like Help->Tooltips). But
On Mon, Dec 09, 2002 at 11:27:30PM +0100, Alfredo Braunstein wrote:
> It looks broken anyway. Maybe it's better to call an external editor
> configurable by preferences?
The preference of an external editor should be stated by setting the EDITOR
environment variale to an appropriate value. No
Andre Poenitz wrote:
> On Mon, Dec 09, 2002 at 11:27:30PM +0100, Alfredo Braunstein wrote:
>> It looks broken anyway. Maybe it's better to call an external editor
>> configurable by preferences?
>
> The preference of an external editor should be stated by setting the
> EDITOR environment variale
On Tue, Dec 10, 2002 at 08:35:53AM +0100, Alfredo Braunstein wrote:
> > The preference of an external editor should be stated by setting the
> > EDITOR environment variale to an appropriate value. No need to re-invent
> > the wheel...
>
> That's how it's implemented right now. The problem is that
Hi.. in the qt frontend, when I do Layout-Preamble, nothing happens,
i.e. no Preamble box pops up... is this a known problem?
Thanks,
nirmal
On Thu Oct 31, 2002 15:06, Nirmal Govind wrote:
Hi.. in the qt frontend, when I do Layout-Preamble, nothing happens,
i.e. no Preamble box pops up... is this a known problem?
you can find it in the document settings dialog
you can find it in the document settings dialog
Ok.. thanks..
Btw, just wanted to mention that the QT frontend is so much better than
xforms.. and I don't mean that just cos of the appearance.. it is really
more efficient.. it takes fewer clicks to do almost anything and
browsing thru
Ok.. one more.. how do I get the Preferences dialog? Edit - Preferences
doesn't pop up anything.. and I tried looking at the other menus but
can't seem to find it..
Also, when I type, there's a significant delay between the keyboard
stroke and the visual.. and if I type continuously then the
Hi.. in the qt frontend, when I do Layout->Preamble, nothing happens,
i.e. no Preamble box pops up... is this a known problem?
Thanks,
nirmal
On Thu Oct 31, 2002 15:06, Nirmal Govind wrote:
> Hi.. in the qt frontend, when I do Layout->Preamble, nothing happens,
> i.e. no Preamble box pops up... is this a known problem?
you can find it in the document settings dialog
>
> you can find it in the document settings dialog
>
Ok.. thanks..
Btw, just wanted to mention that the QT frontend is so much better than
xforms.. and I don't mean that just cos of the appearance.. it is really
more efficient.. it takes fewer clicks to do almost anything and
browsing thru
Ok.. one more.. how do I get the Preferences dialog? Edit -> Preferences
doesn't pop up anything.. and I tried looking at the other menus but
can't seem to find it..
Also, when I type, there's a significant delay between the keyboard
stroke and the visual.. and if I type continuously then the
74 matches
Mail list logo
