> 2025/04/12 7:48、Koji Yokota
> のメール:
>> 2025/04/12 0:46、Richard Kimberly Heck のメール:
>> No, you should update the format in prefs2prefs_prefs.py and in LyXRC.py and
>> configure.py, but that's all you need to do. Have a look at the start of
>> commit 7bf14813d7b.
>>
>> I can do it, if you prefe
> 2025/04/10 23:30、Jean-Marc Lasgouttes のメール:
>
> \ui_theme ?
That would be nice :) I think I’m going with it.
Koji
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel
> 2025/04/12 0:46、Richard Kimberly Heck のメール:
> No, you should update the format in prefs2prefs_prefs.py and in LyXRC.py and
> configure.py, but that's all you need to do. Have a look at the start of
> commit 7bf14813d7b.
>
> I can do it, if you prefer.
I see, thank you. I think I can manage it
On 4/10/25 9:24 PM, Koji Yokota wrote:
2025/04/10 23:01、Richard Kimberly Heck のメール:
Probably not, if I'm following this. That's only needed when preferences are
removed or their semantics is changed. We don't revert.
Does it mean I can just add the command without changing the file format numb
On 4/10/25 9:24 PM, Koji Yokota wrote:
2025/04/10 23:01、Richard Kimberly Heck のメール:
Probably not, if I'm following this. That's only needed when preferences are
removed or their semantics is changed. We don't revert.
Does it mean I can just add the command without changing the file format numb
> 2025/04/10 23:01、Richard Kimberly Heck のメール:
>
> Probably not, if I'm following this. That's only needed when preferences are
> removed or their semantics is changed. We don't revert.
Does it mean I can just add the command without changing the file format number?
Koji
--
lyx-devel mailing l
Le 10/04/2025 à 07:25, Koji Yokota a écrit :
Dear all,
I’m planning to update LYXRC_FILEFORMAT to 40 in a few days to include
\color_theme command for preserving color theme over sessions. If there is any
problem, please let me know.
There may have been an option to give more general command
On Thu, Apr 10, 2025 at 02:25:45PM +0900, Koji Yokota wrote:
> I???m planning to update LYXRC_FILEFORMAT to 40 in a few days to include
> \color_theme command for preserving color theme over sessions. If there is
> any problem, please let me know.
Not a problem, but you might need to update pref
On 4/10/25 9:54 AM, Pavel Sanda wrote:
On Thu, Apr 10, 2025 at 02:25:45PM +0900, Koji Yokota wrote:
I???m planning to update LYXRC_FILEFORMAT to 40 in a few days to include
\color_theme command for preserving color theme over sessions. If there is any
problem, please let me know.
Not a proble
Dear all,
I’m planning to update LYXRC_FILEFORMAT to 40 in a few days to include
\color_theme command for preserving color theme over sessions. If there is any
problem, please let me know.
There may have been an option to give more general command name to it, since
some existing color themes i
Le 7 déc. 2022 à 17:21, Stephan Witt a écrit :
>
> Am 07.12.2022 um 16:21 schrieb Daniel CLEMENT via lyx-users
> :
>>
>> Dear list members,
>>
>> I have monitored last month’s threads about LyX woes under macOS 13. There
>> wasn’t a definite conclusion it seems.
>>
>> Would you say it’s safe
Hi Daniel,
I have used LyX 2.3.6.2 under Ventura and did find that it crashed regularly.
Since the version on LyX.org is still only compiled for Intel, perhaps Rosetta
is the problem.
And just to note, in case it is helpful: if you are familiar with Linux and
have, or don’t mind purchasing, a
I run Ventura on and Intel and on a M1 box and had no problems
whatsoever. I keep Monterey on an iMac and a MacPro (which don't want
to be upgrade to Ventura).
I think the issue is that each major version number upgrade requires a
new installation of the XCode command line tools which seem to inc
Am 07.12.2022 um 16:21 schrieb Daniel CLEMENT via lyx-users
:
>
> Dear list members,
>
> I have monitored last month’s threads about LyX woes under macOS 13. There
> wasn’t a definite conclusion it seems.
>
> Would you say it’s safe to upgrade to MacOS13 now (with LyX 2.3.6.2)?
>
> When I ins
On Sun, Sep 10, 2017 at 02:51:36PM +0200, Uwe Stöhr wrote:
> While reporting compiler warnings in libiconv 1.14 I noticed that version
> 1.15 was released in February this year. So I grabbed the sources from
> https://ftp.gnu.org/pub/gnu/libiconv/
> and updated them in our git master.
>
> It compi
While reporting compiler warnings in libiconv 1.14 I noticed that
version 1.15 was released in February this year. So I grabbed the
sources from
https://ftp.gnu.org/pub/gnu/libiconv/
and updated them in our git master.
It compiles fine and works fine here.
I don't know about Linux. If it is unc
On 07/19/2016 06:50 AM, Michael Berger wrote:
but trying to compile any of my classicthesis-LyX-v4.1 documents I get
either an endless loop or heaps of errors - there are so many different
errors that I eventually gave up trying to fix them
I can't confirm this, even classicthesis for LyX v. 3
On Wed, Jul 20, 2016 at 06:55:25AM +0200, Michael Berger wrote:
>
> To be frank, I am surprised that by now all but two my of old documents
> (Miede's classicthesis) do compile after changing/adapting just one or two
> details - most documents compiled off the cuff!
> And for these two last docume
2013; classicthesis-LyX-v4.1, most of them with the module
'Linguistics' loaded and using different bibliography styles.
After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and
loading those older documents I found the following when trying to export to
PDF:
I don't
1, most of them with the module
> 'Linguistics' loaded and using different bibliography styles.
>
> After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and
> loading those older documents I found the following when trying to export to
> PDF:
I don't know
ageia5 using LyX 2.1;
> TexLive 2013; classicthesis-LyX-v4.1, most of them with the module
> 'Linguistics' loaded and using different bibliography styles.
>
> After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and
> loading those older documents I found the
bliography styles.
After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and
loading those older documents I found the following when trying to
export to PDF:
* Beamer presentations > OK
* All types of Koma-Script documents >> basically OK with some minor
adjustments, i
On Mon, Jun 06, 2016 at 01:57:11PM -0400, Scott Kostyshak wrote:
> On Mon, May 30, 2016 at 12:21:47PM -0400, Scott Kostyshak wrote:
> > On Mon, May 30, 2016 at 02:43:57PM +0200, Charles de Miramon wrote:
> > > Kornel Benko wrote:
> > >
> > > > Knowing what went wrong, why are you doing it again?
>
On Mon, Nov 09, 2015 at 07:37:47AM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > diff --git a/UPGRADING b/UPGRADING
> > index 122f92d..1f410ac 100644
> > --- a/UPGRADING
> > +++ b/UPGRADING
> > @@ -1,6 +1,44 @@
> > -How do I upgrade my existing
Scott Kostyshak wrote:
> diff --git a/UPGRADING b/UPGRADING
> index 122f92d..1f410ac 100644
> --- a/UPGRADING
> +++ b/UPGRADING
> @@ -1,6 +1,44 @@
> -How do I upgrade my existing LyX system to version 2.1.x?
> +How do I upgrade my existing LyX sy
On 3/12/15, Jean-Marc Lasgouttes wrote:
> Because we reconfigure automatically when LyX is newer than the stuff in the
> user directory.
>
> This is nice as long as the installed files are dated to installation time.
>
> JMarc.
But why did a manual reconfigure not solve the problem? Why did he
ha
Because we reconfigure automatically when LyX is newer than the stuff in the
user directory.
This is nice as long as the installed files are dated to installation time.
JMarc.
Le 12 mars 2015 18:22:49 CET, Scott Kostyshak a écrit :
>On Mar 12, 2015 5:56 AM, "Jean-Marc Lasgouttes"
>wrote:
>
>>
On Mar 12, 2015 5:56 AM, "Jean-Marc Lasgouttes" wrote:
>
> After asking the reporter, it turns out that it is because his
lyxrc.default was newer than the configure.py. The configure.py last
modification date is not the date of installation, but the date when the
package got built.
Why is this a
Le 11/03/2015 04:15, Scott Kostyshak a écrit :
I tried the user directory on my computer with 2.1.3 and with master,
and it worked fine for me.
Does anyone have any ideas why this happened? I've seen similar topics
come up from
time to time so I'm wondering if there's a bug lurking somewhere.
T
A user upgraded to Ubuntu 15.04 and LyX would not export (greyed out).
Removing the LyX user directory solved the problem. Reconfigure did
not solve the problem. The user posted the LyX user directory here:
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1430059/+attachment/4340587/+files/lyxdir
Barak Sh wrote:
> In version 1.6.5 of LyX, this behavior was changed for some reason. Now the
> cursor is positioned AFTER the symbol, and not inside it.
> This makes writing equations very cumbersome, as I have to manually move
> the cursor inside the symbol after creating it. Would it be possibl
Hello,
In previous versions of LyX, when using keyboard shortcuts such as Alt+M F =
math-insert \frac, the fraction symbol would be inserted and the cursor
positioned such that the numerator may be entered immediately.
Similarly, Alt+M S (for math-insert \sqrt) would position the cursor inside
the
Jürgen Spitzmüller wrote:
> Does anybody feel confident enough to do this task? I'm a bit reluctant
> doing this myself.
Since nobody stepped forward, I had a go myself and just copied the boost
directory just after Lars' update in rev. 19398 ("Update to latest from boost
1.34.x branch") to bran
Does anybody feel confident enough to do this task? I'm a bit reluctant doing
this myself.
Jürgen
On Friday 31 August 2007 11:05:09 Anand Rangarajan wrote:
> Thanks. I think I'll just recompile lyx directly from the 1.5.x source
> using Qt 4.3.0. My concern is that this could happen to Joe Random User. Qt
> gets upgraded (admittedly a whole point release up) and lyx starts going
> wonky. Are th
José Matos <[EMAIL PROTECTED]> writes:
> In this particular case I would suggest to recompile the original source
> rpm
> that is available, that will fix the qt4 problems and solve also any other
> dependency problems.
>
Thanks. I think I'll just recompile lyx directly from the 1.5.x sour
On Friday 31 August 2007 07:52:09 Abdelrazak Younes wrote:
> Hello,
>
> I don't think anybody ever tested running LyX with a version of Qt
> greater than the one LyX was compiled with...
Probably that means that I am anybody. :-)
I did it sometimes, when I update the installed version of qt4
Anand Rangarajan wrote:
First off, I apologize if this lyx "bug" is well known. The scare quotes
are because it could be a qt bug. [It is a cute bug nevertheless -
sorry, sorry :-)]
Currently, on opensuse 10.2, I have lyx 1.5.1 installed (via a Guru
x86_64 suse rpm). It works fine when linking t
> everything works except for one problem. The (black) cursor is missing.
> I can make out a small dot every once in a while but it vanishes pretty
> soon. When I switched back to libqt4, version 4.2.1, the missing black
> cursor returned - thankfully.
here it works properly (on 4.3.0). have you t
First off, I apologize if this lyx "bug" is well known. The scare quotes
are because it could be a qt bug. [It is a cute bug nevertheless -
sorry, sorry :-)]
Currently, on opensuse 10.2, I have lyx 1.5.1 installed (via a Guru
x86_64 suse rpm). It works fine when linking to libqt4 version 4.2.1.
Wh
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> If nobody complains I will apply this to branch and trunk this
> evening.
It is in now.
JMarc
Mael Hilléreau <[EMAIL PROTECTED]> writes:
> Selon Jean-Marc Lasgouttes <[EMAIL PROTECTED]>:
>
>> Mael Hilléreau <[EMAIL PROTECTED]> writes:
>>
>> > I applied this patch and compiled but I don't know whether it works. What
>> do you
>> > mean by "when I start"? Does it mean that the "preferences.p
On Aug 5, 2007, at 9:44 AM, Jean-Marc Lasgouttes wrote:
Mael Hilléreau <[EMAIL PROTECTED]> writes:
I ran autogen.sh and recompiled from start and now it works fine.
Great!
Is "environment.plist" needed anymore? (I mean for BIBINPUTS,
BSTINPUTS and
DISPLAY)
I'm not sure. Maybe Bennett
Mael Hilléreau <[EMAIL PROTECTED]> writes:
> I ran autogen.sh and recompiled from start and now it works fine.
Great!
> Is "environment.plist" needed anymore? (I mean for BIBINPUTS, BSTINPUTS and
> DISPLAY)
I'm not sure. Maybe Bennett knows.
JMarc
Selon Jean-Marc Lasgouttes <[EMAIL PROTECTED]>:
> Mael Hilléreau <[EMAIL PROTECTED]> writes:
>
> > I applied this patch and compiled but I don't know whether it works. What
> do you
> > mean by "when I start"? Does it mean that the "preferences.plist" is no
> more
> > needed? If yes, it doesn't se
Mael Hilléreau <[EMAIL PROTECTED]> writes:
> I applied this patch and compiled but I don't know whether it works. What do
> you
> mean by "when I start"? Does it mean that the "preferences.plist" is no more
> needed? If yes, it doesn't seem to work for me...
Here I do not have any language defin
Selon Jean-Marc Lasgouttes <[EMAIL PROTECTED]>:
> 2/ gettext 0.14.6 is able to read system settings on the mac, which
> means that my menus are automatically
>translated to french when I start
I applied this patch and compiled but I don't know whether it works. What do you
mean by "when I sta
; The fix is easy - delete the .lyx/ directory. Then start
> LyX again, and the view menu suddenly have a toolbar entry.
>
> The questions:
> Is this ok? Should people upgrading to 1.5 have to throw away
> a possibly customized .lyx directory?
> Or is this only a problem fo
uddenly have a toolbar entry.
The questions:
Is this ok? Should people upgrading to 1.5 have to throw away
a possibly customized .lyx directory?
Or is this only a problem for people like me, who install svn lyx now and then?
And is there a better fix than removing all of ~/.lyx ?
Helge Hafting
Hi
This is just an early warning^H^H^H^H^H^H^H blurb that I'm finally
upgrading the wiki to the new wiki engine. I've finally realised that I'm
unable to guarantee a perfectly smooth transition, so instead I'll just
plunge in and deal with any problems as they occur and get
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| I need to do some upgrading of aussie, so service might go up and down
| a bit.
>
| I'll try to be quick and invisible.
>
| Have patience.
Ok, it seems that my remote upgrading from RH8 to FC1 was successful.
If you have any problems
I need to do some upgrading of aussie, so service might go up and down
a bit.
I'll try to be quick and invisible.
Have patience.
--
Lgb
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> On Tuesday 04 February 2003 2:50 pm, Jean-Marc Lasgouttes
Angus> wrote:
>> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>>
Angus> bugs to the users list or to the devel list?
>> Good question. Maybe devel.
>>
>> Ang
On Tuesday 04 February 2003 2:50 pm, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> bugs to the users list or to the devel list?
>
> Good question. Maybe devel.
>
> Angus, feel free to take over the file and change whatever seems
> reasonable (al
On Tue, Feb 04, 2003 at 02:24:11PM +, Angus Leeming wrote:
>
> Should we provide any hint to users how to find out whether their Qt is
> using Xft2/fontconfig? I certainly have no idea, although I can deduce that
> I am because I know that RH8 users have to download this package.
ldd `which
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
|
| Angus> bugs to the users list or to the devel list?
|
| Good question. Maybe devel.
|
| Angus, feel free to take over the file and change whatever seems
| reasonable (also Jose's su
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> bugs to the users list or to the devel list?
Good question. Maybe devel.
Angus, feel free to take over the file and change whatever seems
reasonable (also Jose's suggestion about warning that xforms 0.89 will
not be supported in 1
On Tuesday 04 February 2003 13:56, Jean-Marc Lasgouttes wrote:
>
> Here is what I came up with. This is the 1.2.3 announcement, with some
> parts of the 1.3.0 NEWS file pasted here and there. Would that suit
> you?
*
Note also that the xforms library has been very recently updated to
version 1
On Tuesday 04 February 2003 2:35 pm, Jean-Marc Lasgouttes wrote:
> Well, when I added this text to NEWS some time ago, I was rather
> surprised that nobody complained about this lame text. Better late
> than never, I guess.
;-)
bugs to the users list or to the devel list?
If you find what you th
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote:
>> Here is what I came up with. This is the 1.2.3 announcement, with
>> some parts of the 1.3.0 NEWS file pasted here and there. Would that
>> suit you?
Angus> Some comments:
Angus> First paragraphs are
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> ** Qt frontend
>> This is of course the most visible new feature. This frontend
>> supports either Qt 2.x or 3.0.x and is mostly feature complete.
Juergen> Qt 2.x or 3.x (up to 3.1.1) actu
Jean-Marc Lasgouttes wrote:
> Here is what I came up with. This is the 1.2.3 announcement, with some
> parts of the 1.3.0 NEWS file pasted here and there. Would that suit
> you?
Some comments:
First paragraphs are very important, and yours doesn't make sense ;-)
(There's nothing to "however".) P
Jean-Marc Lasgouttes wrote:
> ** Qt frontend
> This is of course the most visible new feature. This frontend supports
> either Qt 2.x or 3.0.x and is mostly feature complete.
Qt 2.x or 3.x (up to 3.1.1) actually.
Jürgen
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> | I was thinking of either README or INSTALL, actually.
Lars> Where do we mention required compiler versions? Put it there.
Jean-Marc> OK, done. Now, we wil
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> | I was thinking of either README or INSTALL, actually.
Lars> Where do we mention required compiler versions? Put it there.
OK, done. Now, we will need an ANNOUNCE file which is up to date. Do
you want me to cook one based on
lt;[EMAIL PROTECTED]> writes:
| Lars> |
| Lars> | Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
| Lars> writes: | | Lars> Here another update to UPGRADING. Lars, is
| Lars> that OK?
| Lars> |
| Lars> | Lars> Looks ok... are the changes to NEWS something we
s> Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
Lars> writes: | | Lars> Here another update to UPGRADING. Lars, is
Lars> that OK?
Lars> |
Lars> | Lars> Looks ok... are the changes to NEWS something we want in
Lars> 1.3.0?
Lars> |
Lars> | Well, 1.3.0 is the version that
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| >>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
| Lars> Here another update to UPGRADING. Lars, is that OK?
|
| Lars&
>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
Lars> Here another update to UPGRADING. Lars, is that OK?
Lars> Looks ok... are the changes to NEWS something we want in 1.3.0
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| Here another update to UPGRADING. Lars, is that OK?
Looks ok... are the changes to NEWS something we want in 1.3.0?
| Also, Lars could you update INSTALL.autoconf from the INSTALL file of
| the version of autoconf you plan to use, and
On Tuesday 04 February 2003 10:55, Jean-Marc Lasgouttes wrote:
> Here another update to UPGRADING. Lars, is that OK?
>
> Also, Lars could you update INSTALL.autoconf from the INSTALL file of
> the version of autoconf you plan to use, and ABOUT-NLS from gettext?
>
> We should te
Here another update to UPGRADING. Lars, is that OK?
Also, Lars could you update INSTALL.autoconf from the INSTALL file of
the version of autoconf you plan to use, and ABOUT-NLS from gettext?
We should tell somewhere which version of Python is needed (1.5?)
JMarc
? config.h.in
Index
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I guess we need to update this file for 1.3.x.
Sure. And also README (xforms 1.0, qt, amuybe take versioning
discussion from the new stuff I wrote for the web site), INSTALL
(xforms, qt), take new INSTALL.autoconf from autoconf
I guess we need to update this file for 1.3.x.
--
Lgb
RCS file: /usr/local/lyx/cvsroot/lyx-devel/ChangeLog,v
retrieving revision 1.848
diff -u -r1.848 ChangeLog
--- ChangeLog 26 Apr 2002 16:01:39 - 1.848
+++ ChangeLog 1 May 2002 02:09:53 -
@@ -1,3 +1,7 @@
+2002-05-01 John Levon <[EMAIL PROTECTED]>
+
+
hould work too.
>
| OTOH I can whip a patch to UPGRADING if you're not happy with this.
>
| After all, they are using a broken version of convert (I think).
Then I think it is bad to penalize users with a correct convert,
either we should have a check for a faulty one, or just document it
On Wed, May 01, 2002 at 03:45:13AM +0200, Lars Gullik Bjønnes wrote:
> | 2) the convert -depth 8 workaround is going in
>
> as a blanket fix? Or just for certain versions of convert?
Blanket I guess. -depth 16 should work too.
OTOH I can whip a patch to UPGRADING if you're not h
John Levon <[EMAIL PROTECTED]> writes:
| OK, a little more descriptive. This assumes :
>
| 1) Dekel's floatingfigure patch isn't going in
It seems that this has some more implications yes.
So it will probably not go in.
| 2) the convert -depth 8 workaround is going in
as a blanket fix? Or just
x-devel/ChangeLog,v
retrieving revision 1.848
diff -u -r1.848 ChangeLog
--- ChangeLog 26 Apr 2002 16:01:39 - 1.848
+++ ChangeLog 1 May 2002 01:27:17 -
@@ -1,3 +1,7 @@
+2002-05-01 John Levon <[EMAIL PROTECTED]>
+
+ * UPGRADING: more details on upgrading
+
2002-04-26 La
> "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes:
Garst> Jean-Marc Lasgouttes wrote:
>>
>> - the "Latex" font style does not exist anymore. If you really need
>> its functionality, consider using the "PassThru" keyword instead.
>>
>> The new layout format keywords are described in the
I did some further changes to UPGRADING (after the ones from Lars). I
append the result, because I would like people to comment on what they
needed to do to upgrade.
JMarc
How do I upgrade my existing LyX system to version 1.2.x?
-
If
81 matches
Mail list logo
