On 5/15/24 17:47, Jean-Marc Lasgouttes wrote:
Le 11/04/2024 à 23:55, Jean-Marc Lasgouttes a écrit :
Le 11/04/2024 à 18:21, Stephan Witt a écrit :
Is it new to master (i.e., the biginset branch)?
I think it’s new.
If you have time to make a video I would be interested to see it
because I
Le 11/04/2024 à 23:55, Jean-Marc Lasgouttes a écrit :
Le 11/04/2024 à 18:21, Stephan Witt a écrit :
Is it new to master (i.e., the biginset branch)?
I think it’s new.
If you have time to make a video I would be interested to see it
because I cannot reproduce on X (I have to try Wayland).
Am 11.04.2024 um 23:55 schrieb Jean-Marc Lasgouttes :
>
> Le 11/04/2024 à 18:21, Stephan Witt a écrit :
>>> Is it new to master (i.e., the biginset branch)?
>> I think it’s new.
>>> If you have time to make a video I would be interested to see it because I
>>> cannot reproduce on X (I have to
Le 11/04/2024 à 18:21, Stephan Witt a écrit :
Is it new to master (i.e., the biginset branch)?
I think it’s new.
If you have time to make a video I would be interested to see it because I
cannot reproduce on X (I have to try Wayland).
Yes, I made two videos - one for 2.3.6.2 and one for
On Thu, Apr 11, 2024 at 04:35:00PM GMT, Richard Kimberly Heck wrote:
> On 4/11/24 15:50, Scott Kostyshak wrote:
> > I can't reproduce the issue, but I also can't redock my outline window.
> > Meaning, no matter where I drag it, it doesn't snap to anywhere. I've
> > never tried to do it before, so
On 4/11/24 15:50, Scott Kostyshak wrote:
I can't reproduce the issue, but I also can't redock my outline window.
Meaning, no matter where I drag it, it doesn't snap to anywhere. I've
never tried to do it before, so I don't know if it's a wayland/linux
issue.
I believe that is a known Wayland
On Thu, Apr 11, 2024 at 06:21:52PM GMT, Stephan Witt wrote:
> Am 11.04.2024 um 16:59 schrieb Jean-Marc Lasgouttes :
> >
> > Le 10/04/2024 à 18:52, Stephan Witt a écrit :
> >> Am 10.04.2024 um 15:10 schrieb Jean-Marc Lasgouttes :
> >>>
> >>> Le 10/04/2024 à 15:09, Kornel Benko a écrit :
>
Am 11.04.2024 um 16:59 schrieb Jean-Marc Lasgouttes :
>
> Le 10/04/2024 à 18:52, Stephan Witt a écrit :
>> Am 10.04.2024 um 15:10 schrieb Jean-Marc Lasgouttes :
>>>
>>> Le 10/04/2024 à 15:09, Kornel Benko a écrit :
This patch definitely cured the behaviour here.
>>>
>>> Thanks for testing.
Le 10/04/2024 à 18:52, Stephan Witt a écrit :
Am 10.04.2024 um 15:10 schrieb Jean-Marc Lasgouttes :
Le 10/04/2024 à 15:09, Kornel Benko a écrit :
This patch definitely cured the behaviour here.
Thanks for testing. Both for the math and the minibuffer examples? (this is
what I see, but I
Am 10.04.2024 um 15:10 schrieb Jean-Marc Lasgouttes :
>
> Le 10/04/2024 à 15:09, Kornel Benko a écrit :
>> This patch definitely cured the behaviour here.
>
> Thanks for testing. Both for the math and the minibuffer examples? (this is
> what I see, but I want to be sure).
>
> The problem is
On Wed, Apr 10, 2024 at 03:29:43PM GMT, Jean-Marc Lasgouttes wrote:
> Le 10/04/2024 à 15:32, Kornel Benko a écrit :
> > I confess tested only the math example.
> > But the first 10 tries with the command buffer did OK too
>
> Thanks a lot. I'll put it in.
Tested briefly and looks good! I'll
Le 10/04/2024 à 15:32, Kornel Benko a écrit :
I confess tested only the math example.
But the first 10 tries with the command buffer did OK too
Thanks a lot. I'll put it in.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Wed, 10 Apr 2024 15:10:04 +0200
schrieb Jean-Marc Lasgouttes :
> Le 10/04/2024 à 15:09, Kornel Benko a écrit :
> > This patch definitely cured the behaviour here.
>
> Thanks for testing. Both for the math and the minibuffer examples? (this
> is what I see, but I want to be sure).
>
> The
Le 10/04/2024 à 15:09, Kornel Benko a écrit :
This patch definitely cured the behaviour here.
Thanks for testing. Both for the math and the minibuffer examples? (this
is what I see, but I want to be sure).
The problem is that most of the biginset branch was developed and
debugged using the
Am Wed, 10 Apr 2024 14:19:03 +0200
schrieb Jean-Marc Lasgouttes :
> Le 09/04/2024 à 22:26, Scott Kostyshak a écrit :
> > Bisect leads to here: 5e857883. Interestingly I bisected on the command
> > buffer recipe, but the commit talks about math but I guess they're
> > related issues.
>
> What
Le 09/04/2024 à 22:26, Scott Kostyshak a écrit :
Bisect leads to here: 5e857883. Interestingly I bisected on the command
buffer recipe, but the commit talks about math but I guess they're
related issues.
What about this, which fixes up another commit?
JMarc
From
On Tue, Apr 09, 2024 at 04:26:36PM GMT, Scott Kostyshak wrote:
> On Tue, Apr 09, 2024 at 01:27:42PM GMT, Scott Kostyshak wrote:
> > On Tue, Apr 09, 2024 at 06:47:14PM GMT, Jean-Marc Lasgouttes wrote:
> > > Le 09/04/2024 à 16:48, Scott Kostyshak a écrit :
> > > > > Ohh, nice! What I do not
On Tue, Apr 09, 2024 at 01:27:42PM GMT, Scott Kostyshak wrote:
> On Tue, Apr 09, 2024 at 06:47:14PM GMT, Jean-Marc Lasgouttes wrote:
> > Le 09/04/2024 à 16:48, Scott Kostyshak a écrit :
> > > > Ohh, nice! What I do not understand is why the text (but not the insets)
> > > > moves up when opening
On Tue, Apr 09, 2024 at 06:47:14PM GMT, Jean-Marc Lasgouttes wrote:
> Le 09/04/2024 à 16:48, Scott Kostyshak a écrit :
> > > Ohh, nice! What I do not understand is why the text (but not the insets)
> > > moves up when opening the minibuffer. This is strange.
> >
> > Ah interesting, I didn't
Le 09/04/2024 à 16:48, Scott Kostyshak a écrit :
Ohh, nice! What I do not understand is why the text (but not the insets)
moves up when opening the minibuffer. This is strange.
Ah interesting, I didn't notice that. Strange indeed.
If you feel like bisecting, do not hesitate ;) I am not sure
On Tue, Apr 09, 2024 at 12:20:34PM GMT, Jean-Marc Lasgouttes wrote:
> Le 09/04/2024 à 06:51, Scott Kostyshak a écrit :
> > > Can anyone reproduce weirdness after (4)?
>
> Hi Scott,
>
> Yes, I can, but I did not find the time to investigate it yet.
No problem! Good to know you can reproduce.
>
Le 09/04/2024 à 06:51, Scott Kostyshak a écrit :
Can anyone reproduce weirdness after (4)?
Hi Scott,
Yes, I can, but I did not find the time to investigate it yet.
I can still reproduce on current master. Another way to reproduce, which
doesn't involve math, is the following:
(1) Help >
On Fri, Apr 05, 2024 at 12:52:25PM GMT, Scott Kostyshak wrote:
> On Fri, Apr 05, 2024 at 04:17:10PM GMT, Jean-Marc Lasgouttes wrote:
> > I merged the biginset branch (see #12297 for context) to master. This is the
> > good part.
> >
> > The bad part is that I decided first to rebase it over
Am Freitag, dem 05.04.2024 um 16:17 +0200 schrieb Jean-Marc Lasgouttes:
> What now? Well, testing is welcome when you have time : does
> everything works the same, but faster for big document that were
> annoying?.
I see drawing omissions with change tracking. Select part of a word
with CT on and
On Fri, Apr 05, 2024 at 04:17:10PM GMT, Jean-Marc Lasgouttes wrote:
> I merged the biginset branch (see #12297 for context) to master. This is the
> good part.
>
> The bad part is that I decided first to rebase it over master, and that
> resulted in 100+ messages sent to lyx-devel :( We are
I merged the biginset branch (see #12297 for context) to master. This is
the good part.
The bad part is that I decided first to rebase it over master, and that
resulted in 100+ messages sent to lyx-devel :( We are investigating how
to avoid that.
What now? Well, testing is welcome when you
On Sun, Apr 1, 2012 at 6:32 PM, rgh...@lyx.org wrote:
Author: Richard Heck rgh...@lyx.org
Date: Sun, 01 Apr 2012 18:32:10 -0400
New Commit: 6b5e8b3e835af4806944f1d957f9e5bdbb892371
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=6b5e8b3e835af4806944f1d957f9e5bdbb892371
Log:
Sorry, I didn't
:
http://git.lyx.org/?p=lyx.git;a=commit;h=6b5e8b3e835af4806944f1d957f9e5bdbb892371
Log:
Sorry, I didn't mean to include this change from trunk.
That said, Julien, if you see this, is that something we
should think about backporting?
If it compiles, then why not? Please go ahead
1d957f9e5bdbb892371
>
> Log:
> Sorry, I didn't mean to include this change from trunk.
>
> That said, Julien, if you see this, is that something we
> should think about backporting?
>
>
If it compiles, then why not? Please go ahead.
Cheers,
Julien
6944f1d957f9e5bdbb892371
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=6b5e8b3e835af4806944f1d957f9e5bdbb892371
Log:
Sorry, I didn't mean to include this change from trunk.
That said, Julien, if you see this, is that something we
should think about backporting?
If it compiles,
On May 31, 2011, at 11:18 PM, Christian Ridderström wrote:
Hi,
I'm trying to figure out if my mails get through or not...
They get through...
/Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
Are you aware that your phone number is visible to the rest of the world?
Hi Abdel and Tommaso,
Thanks for letting me know my posts do come through. Now I'm getting
them as well:-) Apparently 'BCC:ing' the list doesn't work.
Oh, and thanks for letting me know my cell phone number is visible. I
know about it and have left it as that on purpose. My reasoning is
that it
On May 31, 2011, at 11:18 PM, Christian Ridderström wrote:
> Hi,
>
> I'm trying to figure out if my mails get through or not...
They get through...
> /Christian
>
> --
> Christian Ridderström, Cell phone: +46-70 687 39 44
Are you aware that your phone number is visible to the rest of the
Hi Abdel and Tommaso,
Thanks for letting me know my posts do come through. Now I'm getting
them as well:-) Apparently 'BCC:ing' the list doesn't work.
Oh, and thanks for letting me know my cell phone number is visible. I
know about it and have left it as that on purpose. My reasoning is
that it
Hi,
I'm trying to figure out if my mails get through or not...
/Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
Hi,
I'm trying to figure out if my mails get through or not...
/Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
And this time it is not the same as before.
And it belongs to Pavel's changes.
...
[ 14%] Building CXX object
src/frontends/qt4/CMakeFiles/frontend_qt4.dir/usr/src/lyx/lyx-devel/src/frontends/qt4/GuiPrefs.o
cd /usr/BUILD/BuildLyx/src/frontends/qt4 /usr/local/bin/c++ -DQT_NO_STL
And this time it is not the same as before.
And it belongs to Pavel's changes.
...
[ 14%] Building CXX object
src/frontends/qt4/CMakeFiles/frontend_qt4.dir/usr/src/lyx/lyx-devel/src/frontends/qt4/GuiPrefs.o
cd /usr/BUILD/BuildLyx/src/frontends/qt4 && /usr/local/bin/c++ -DQT_NO_STL
.. finished now.
I couldn't stand it any longer, and once I started I couldn't stop.
Vincent
.. finished now.
I couldn't stand it any longer, and once I started I couldn't stop.
Vincent
rgheck wrote:
Sure, but the ERT should not be in the Part style anyway.
Put it alone on a standard style line and compilation works all right.
But then, so far as I can see, the ERT is on the next page, and the
attempt to turn off the page number fails.
Granted, this should really
On Sat, 2009-03-21 at 09:12 +0100, Jürgen Spitzmüller wrote:
rgheck wrote:
Sure, but the ERT should not be in the Part style anyway.
Put it alone on a standard style line and compilation works all right.
But then, so far as I can see, the ERT is on the next page, and the
Waluyo Adi Siswanto wrote:
PS.: perhaps the error message is not the appropriate one?
Maybe. But it is generated by TeX...
Jürgen
rgheck wrote:
> > Sure, but the ERT should not be in the Part style anyway.
> > Put it alone on a standard style line and compilation works all right.
> >
> >
>
> But then, so far as I can see, the ERT is on the next page, and the
> attempt to turn off the page number fails.
>
> Granted, this
On Sat, 2009-03-21 at 09:12 +0100, Jürgen Spitzmüller wrote:
> rgheck wrote:
> > > Sure, but the ERT should not be in the Part style anyway.
> > > Put it alone on a standard style line and compilation works all right.
> > >
> > >
> >
> > But then, so far as I can see, the ERT is on the next
Waluyo Adi Siswanto wrote:
> PS.: perhaps the error message is not the appropriate one?
Maybe. But it is generated by TeX...
Jürgen
Waluyo Adi Siswanto wrote:
Actually I have a problem (in LyX 1.6.2) when I want to set the page
without number under the Part environment using ERT
\thispagestyle{empty}. The document class is book(koma-script).
What a surprise, View PDF, LyX error appears TeX capacity exceeded:
sorry, main
The difference is that hyperref is turned on in the 1.6.2 version. If
you turn it off, you don't get the error.
rh
It doesn't help. It works if the environment changed to Part* instead of
Part. So in Part* it is possible to have a clean page without page
number, but Part would be
Waluyo Adi Siswanto wrote:
It doesn't help. It works if the environment changed to Part* instead of
Part. So in Part* it is possible to have a clean page without page
number, but Part would be difficult. And to me the error message is
unusual as it is pointing to TeX capacity exceeded?
rgheck rgh...@... writes:
Waluyo Adi Siswanto wrote:
Actually I have a problem (in LyX 1.6.2) when I want to set the page
without number under the Part environment using ERT
\thispagestyle{empty}. The document class is book(koma-script).
[...]
The difference is that hyperref is turned
Jean-Pierre Chrétien wrote:
rgheck rgh...@... writes:
Waluyo Adi Siswanto wrote:
Actually I have a problem (in LyX 1.6.2) when I want to set the page
without number under the Part environment using ERT
\thispagestyle{empty}. The document class is book(koma-script).
[...]
Waluyo Adi Siswanto wrote:
Actually I have a problem (in LyX 1.6.2) when I want to set the page
without number under the Part environment using ERT
\thispagestyle{empty}. The document class is book(koma-script).
What a surprise, View PDF, LyX error appears "TeX capacity exceeded:
sorry,
> >
> The difference is that hyperref is turned on in the 1.6.2 version. If
> you turn it off, you don't get the error.
>
> rh
>
It doesn't help. It works if the environment changed to Part* instead of
Part. So in Part* it is possible to have a clean page without page
number, but Part
Waluyo Adi Siswanto wrote:
> It doesn't help. It works if the environment changed to Part* instead of
> Part. So in Part* it is possible to have a clean page without page
> number, but Part would be difficult. And to me the error message is
> unusual as it is pointing to TeX capacity exceeded?
>
rgheck writes:
>
> Waluyo Adi Siswanto wrote:
> > Actually I have a problem (in LyX 1.6.2) when I want to set the page
> > without number under the Part environment using ERT
> > \thispagestyle{empty}. The document class is book(koma-script).
[...]
> The difference is that hyperref
Jean-Pierre Chrétien wrote:
rgheck writes:
Waluyo Adi Siswanto wrote:
Actually I have a problem (in LyX 1.6.2) when I want to set the page
without number under the Part environment using ERT
\thispagestyle{empty}. The document class is book(koma-script).
[...]
Actually I have a problem (in LyX 1.6.2) when I want to set the page
without number under the Part environment using ERT
\thispagestyle{empty}. The document class is book(koma-script).
What a surprise, View PDF, LyX error appears TeX capacity exceeded:
sorry, main memory [main memory size=150
Actually I have a problem (in LyX 1.6.2) when I want to set the page
without number under the Part environment using ERT
\thispagestyle{empty}. The document class is book(koma-script).
What a surprise, View PDF, LyX error appears "TeX capacity exceeded:
sorry, main memory [main memory size=15
and i would add: no individual embedding (like in odf i guess)
(which would probably boil down to something very similar like this:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg138780.html)
Edwin,
I have seen this link a few times, are you sure you want to propose
your idea? We
Bo Peng wrote:
and i would add: no individual embedding (like in odf i guess)
(which would probably boil down to something very similar like this:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg138780.html)
With the details worked out, I think this is pretty similar to what I've
With the details worked out, I think this is pretty similar to what I've
got.
That is great. Then we do not have a new proposal to worry about (if
Edwin agrees).
Bo
> and i would add: no individual embedding (like in odf i guess)
>
> (which would probably boil down to something very similar like this:
> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg138780.html)
Edwin,
I have seen this link a few times, are you sure you want to propose
your idea? We
Bo Peng wrote:
and i would add: no individual embedding (like in odf i guess)
(which would probably boil down to something very similar like this:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg138780.html)
With the details worked out, I think this is pretty similar to what I've
> With the details worked out, I think this is pretty similar to what I've
> got.
That is great. Then we do not have a new proposal to worry about (if
Edwin agrees).
Bo
Sebastian Zschernig wrote:
Vorschläge für Verbesserungen:
1. Es fehlt (oder ich finde nicht) für LyX eine Verzeichnis aller LyX
Befehle.
http://wiki.lyx.org/LyX/LyxFunctions
2. Was auch schön wäre: ein shortcut (bzw. bind-barer Befehl), der ein
aufgeklapptes ert-Fenster, in dem der Cursor
On 12.04.05, Sebastian Zschernig wrote:
Vorschläge für Verbesserungen:
1. Es fehlt (oder ich finde nicht) für LyX eine Verzeichnis aller LyX
Befehle.
There is a list of lyx functions at the lyx WiKi
http://wiki.lyx.org/LyX/LyxFunctions
However, many functions are listed without help text.
Sebastian Zschernig wrote:
> Vorschläge für Verbesserungen:
> 1. Es fehlt (oder ich finde nicht) für LyX eine Verzeichnis aller LyX
> Befehle.
http://wiki.lyx.org/LyX/LyxFunctions
> 2. Was auch schön wäre: ein shortcut (bzw. bind-barer Befehl), der ein
> aufgeklapptes ert-Fenster, in dem der
On 12.04.05, Sebastian Zschernig wrote:
>
>
> Vorschläge für Verbesserungen:
> 1. Es fehlt (oder ich finde nicht) für LyX eine Verzeichnis aller LyX
> Befehle.
There is a list of lyx functions at the lyx WiKi
http://wiki.lyx.org/LyX/LyxFunctions
However, many functions are listed without help
Vorschlge fr Verbesserungen:
1. Es fehlt (oder ich finde nicht) fr LyX eine Verzeichnis aller LyX
Befehle.
Was ich damit meine:
Die verschiedenen Dateien in .../lyx/bind/ enthalten ja jeweils in der
zweiten Spalte sehr viele Befehle. Aber eben nicht alle. Und dabei
wre eine solche bersicht so
Vorschläge für Verbesserungen:
1. Es fehlt (oder ich finde nicht) für LyX eine Verzeichnis aller LyX
Befehle.
Was ich damit meine:
Die verschiedenen Dateien in .../lyx/bind/ enthalten ja jeweils "in der
zweiten Spalte" sehr viele Befehle. Aber eben nicht alle. Und dabei
wäre eine solche
Sorry gals and guys, I was not paying enough attention to my daily automatic
upgrading procedure, and the Wednesday Python upgrade did not work with the
installed version of the antispam software TMDA. I now also updated TMDA,
and I am now monitoring closely for any troubles. There may be some
Sorry gals and guys, I was not paying enough attention to my daily automatic
upgrading procedure, and the Wednesday Python upgrade did not work with the
installed version of the antispam software TMDA. I now also updated TMDA,
and I am now monitoring closely for any troubles. There may be some
Ooops...
I found the links to the ports, sorry to have bothered you!
I was under the impression that Win32 was the only available
choice for Lyx.
I will check out the page of Tomoharu Nishino.
Kind regards, Tommy.
Ooops...
I found the links to the ports, sorry to have bothered you!
I was under the impression that Win32 was the only available
choice for Lyx.
I will check out the page of Tomoharu Nishino.
Kind regards, Tommy.
John Levon [EMAIL PROTECTED] writes:
| Sorry to bring it up again, but why is this here ? It's not respected in
| screen.C, and you can get the same effect simply by removing banner.xpm
Which is absolutely not the solution to having a bannerless lyx.
Either we alsways show the banner, _or_ we
John Levon <[EMAIL PROTECTED]> writes:
| Sorry to bring it up again, but why is this here ? It's not respected in
| screen.C, and you can get the same effect simply by removing banner.xpm
Which is absolutely not the solution to having a bannerless lyx.
Either we alsways show the banner
It seems that Mate has finally fixed my attachment problem. So let's
attach this darn bashrc again.
JMarc
.bashrc
Description: Binary data
It seems that Mate has finally fixed my attachment problem. So let's
attach this darn bashrc again.
JMarc
.bashrc
Description: Binary data
.bashrc
Description: Binary data
.bashrc
Description: Binary data
For some people, mails might have bounced from the server. Really sorry
about that; the hard disk Gods have been playing a game here.
Please contact me with including the bounce in the message if things still
not in order:
[EMAIL PROTECTED]
or
[EMAIL PROTECTED]
Mate
For some people, mails might have bounced from the server. Really sorry
about that; the hard disk Gods have been playing a game here.
Please contact me with including the bounce in the message if things still
not in order:
[EMAIL PROTECTED]
or
[EMAIL PROTECTED]
Mate
Hi,
sorry, I noticed that the patch mail was pretty long after having sent it.
But would I have had another option? Can I upload a patch somewhere to have
it checked and commited?
Kalle
--
Matthias Kalle Dalheimer
President CEO/VD
Klarlvdalens Datakonsult AB
Fax +46-563-540028
Email [EMAIL
Hi,
sorry, I noticed that the patch mail was pretty long after having sent it.
But would I have had another option? Can I upload a patch somewhere to have
it checked and commited?
Kalle
--
Matthias Kalle Dalheimer
President & CEO/VD
Klarälvdalens Datakonsult AB
Fax +46-563-540028
E
"Michael" == Michael Schmitt [EMAIL PROTECTED] writes:
Michael Sorry, one of our students included a couple of figures in
Michael his lyx document, resized the eps files and the like. During
Michael one of these operations (we do not know what it actually was)
Michael the followi
>>>>> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> Sorry, one of our students included a couple of figures in
Michael> his lyx document, resized the eps files and the like. During
Michael> one of these operations (we do not know what
"Asger" == Asger Alstrup Nielsen [EMAIL PROTECTED] writes:
One question is: Can XForm handle short cuts descriptions in the
menues aka Motif/Mac, i.e. "Cut C-x" instead of "_C_ut"?
Asger Yes and no. It can't do it automatically, but I *think* there
Asger is a meta-character available that
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> One question is: Can XForm handle short cuts descriptions in the
>> menues aka Motif/Mac, i.e. "Cut C-x" instead of "_C_ut"?
Asger> Yes and no. It can't do it automatically, but I *think* there
Asger> is a meta-character
After finishing this mail I decided to CC the LyXList, we talk about
translating menues/key bindings to german... Maybe german
understanders are interested...
One question is: Can XForm handle short cuts descriptions in the
menues aka Motif/Mac, i.e. "CutC-x" instead of "_C_ut"?
Fred
On
After finishing this mail I decided to CC the LyXList, we talk about
translating menues/key bindings to german... Maybe german
understanders are interested...
One question is: Can XForm handle short cuts descriptions in the
menues aka Motif/Mac, i.e. "CutC-x" instead of "_C_ut"?
Fred
On
90 matches
Mail list logo