Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Steve Litt
Peter said on Tue, 31 Oct 2023 09:31:13 +

>Hi, I have just upgraded to Debian 12 and find Lyx will not load.  In
>addition, trying to load it seems to crash xorg, so the only way out
>is to reboot. 

Is your video card an nVidea? In the Linux world, friends don't let
friends use nVidea. Because of their ultra-paranoid secrecy on their
interfaces, the Free Software world has a very hard time making drivers
for their cards, and my experience is that their proprietary drivers are
intermittent and defective also. If you don't believe me, search the
web. If you have an nVidea graphics card, a simple change to Debian's
nVidea graphics drivers could be causing this, and good luck finding
the magic sauce to fix this intermittent.

If this is a laptop, you can't replace the video card, so your best bet
is to join MANY Linux User Group (LUG) mailing lists, and see if people
can help you find this year's secret sauce configuration for your
particular nVidea video interface.

If it's a desktop, I recommend buying yourself a nice Radeon or Intel
video card to replace your nVidea card or supplant your Mobo hosted
nVidea graphic interface, and then use the bios to turn off the
built-in. Either way, once you've gotten rid of your nVidea graphic
hardware, uninstall all the nVidea graphic software and drivers.

If switching out of nVidea doesn't fix the problem, that's fine, you've
improved your computer anyway, and you'll have ruled out a huge chunk
or X crash causes. I know this will be responded to by tens of people
saying their nVidea video interfaces work just fine. This is true, but
when nVidea graphic interfaces cause problems, they take days to
troubleshoot.

If you don't currently have an nVidea graphic interface, please
disregard this post.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Steve Litt
Peter said on Wed, 1 Nov 2023 11:08:10 +

>The next step will be to try and
>find a Fluxbox alternative, maybe a tiling WM, and see if that works.
>Also it gives something definite to go on, and I can take it to the
>Fluxbox list.  A pity because I've found Fluxbox just about perfect.
>Obviously its not for everyone.

I HIGHLY recommend Openbox. I've been using it for almost a decade and
it's perfect. A very similar window manager is ctwm, which I also
recommend. With either, I recommend using dmenu as your main program
launcher.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Steve Litt
Peter said on Wed, 1 Nov 2023 08:47:18 +

>I'll have a go with some of the other suggestions next.  I guess one
>obvious one is to install KDE andtry it with that, since someone
>reports having no problems with that on Debian 12.  Can always take it
>out afterwards.  Or maybe beta 2.4.

Also, you can try starting up your GUI with xinit so you have no
window manager at all, run LyX from an xterm, and see if funky things
still happen.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Eckhard Höffner
You can install several window manager and choose which one you want to
use. So you may add LXQT minimal and then try it again with fluxbox. If it
does not work, you can use LXQT, which should run without any problems.


Peter  schrieb am Mi., 1. Nov. 2023, 12:08:

> Its Fluxbox!
>
> I couldn't bring myself to install KDE, you can imagine that for a Fluxbox
> user that might be a step too far!  So I installed MATE, and Lyx appears to
> start up quite normally, all the recently opened files are there, and it
> looks like it will work.  That's a relief, at least its going to be
> possible to run it.  The next step will be to try and find a Fluxbox
> alternative, maybe a tiling WM, and see if that works.  Also it gives
> something definite to go on, and I can take it to the Fluxbox list.  A pity
> because I've found Fluxbox just about perfect.  Obviously its not for
> everyone.
>
> Thanks again for the suggestions.
>
> Peter
>
>
> On Wed, 01 Nov 2023 09:52:08 +
> lyx-users-requ...@lists.lyx.org wrote:
>
> > Send lyx-users mailing list submissions to
> >   lyx-users@lists.lyx.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >   http://lists.lyx.org/mailman/listinfo/lyx-users
> > or, via email, send a message with subject or body 'help' to
> >   lyx-users-requ...@lists.lyx.org
> >
> > You can reach the person managing the list at
> >   lyx-users-ow...@lists.lyx.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of lyx-users digest..."
> >
> >
> > Today's Topics:
> >
> >1. Re: Debian 12 and Lyx 2.3.7-1 (Folsk Pratima)
> >2. Re: Debian 12 and Lyx 2.3.7-1 (Folsk Pratima)
> >3. Re: Debian 12 and Lyx 2.3.7-1 (Peter)
> >4. Re: Debian 12 and Lyx 2.3.7-1 (Folsk Pratima)
> >
> >
> > --
> >
> > Message: 1
> > Date: Wed, 1 Nov 2023 10:22:54 +0200
> > From: Folsk Pratima 
> > To: lyx-users@lists.lyx.org
> > Subject: Re: Debian 12 and Lyx 2.3.7-1
> > Message-ID: <20231101102254.69039...@void.wired-node-303707.moe>
> > Content-Type: text/plain; charset=US-ASCII
> >
> > See here:
> > http://lists.lyx.org/pipermail/lyx-users/2023-November/005981.html
> >
> > Something went wrong and I created a new thread...
> >
> >
> > --
> >
> > Message: 2
> > Date: Wed, 1 Nov 2023 10:23:48 +0200
> > From: Folsk Pratima 
> > To: lyx-users@lists.lyx.org
> > Subject: Re: Debian 12 and Lyx 2.3.7-1
> > Message-ID: <20231101102348.022a8...@void.wired-node-303707.moe>
> > Content-Type: text/plain; charset=US-ASCII
> >
> > :'(
> >
> >
> > --
> >
> > Message: 3
> > Date: Wed, 1 Nov 2023 08:47:18 +
> > From: Peter 
> > To: "lyx-users@lists.lyx.org" 
> > Subject: Re: Debian 12 and Lyx 2.3.7-1
> > Message-ID: <20231101084718.64a4bde4@silverstone>
> > Content-Type: text/plain; charset=US-ASCII
> >
> > Thanks so much for the suggestions!
> >
> > I ran (as myself) QT-DEBUG, and the same thing happened.  Blank screen,
> but lyx was showing in the bottom fluxbox menu bar, so I quickly closed the
> app and managed to avoid the crash, and thus was able to copy the terminal
> output.  It was as follows.  Sorry, its very long.  It means nothing to
> me.  I'm a long time Debian user, but no sort of serious programming
> background.
> >
> > I'll have a go with some of the other suggestions next.  I guess one
> obvious one is to install KDE andtry it with that, since someone reports
> having no problems with that on Debian 12.  Can always take it out
> afterwards.  Or maybe beta 2.4.
> >
> > Peter
> >
> > [regular user]~$ QT_DEBUG_PLUGINS=1 lyx
> > QFactoryLoader::QFactoryLoader() checking directory path
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms" ...
> > QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so"
> > Found metadata in lib
> /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so, metadata=
> > {
> > "IID":
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> > "MetaData": {
> > "Keys": [
> > "eglfs"
> > ]
> > },
> > "archreq": 0,
> > "className": "QEglFSIntegrationPlugin",
> > "debug": false,
> > "version": 331520
> > }
> >
> >
> > Got keys from plugin meta data ("eglfs")
> > QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so"
> > Found metadata in lib
> /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so, metadata=
> > {
> > "IID":
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> > "MetaData": {
> > "Keys": [
> > "linuxfb"
> > ]
> > },
> > "archreq": 0,
> > "className": "QLinuxFbIntegrationPlugin",
> > "debug": false,
> > "version": 331520
> > }
> >
> >
> > Got keys from plugin meta data ("linuxfb")
> > 

Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Folsk Pratima
On Wed, 1 Nov 2023 12:19:15 +
Peter wrote:

> Yes, its definitely Fluxbox.  I installed ICEWM, and Lyx loads
> perfectly in it too.  What an annoyance!
> 
> Peter

See here:
http://lists.lyx.org/pipermail/lyx-devel/2023-November/010995.html
You might want to participate.
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Peter
Its Fluxbox!

I couldn't bring myself to install KDE, you can imagine that for a Fluxbox user 
that might be a step too far!  So I installed MATE, and Lyx appears to start up 
quite normally, all the recently opened files are there, and it looks like it 
will work.  That's a relief, at least its going to be possible to run it.  The 
next step will be to try and find a Fluxbox alternative, maybe a tiling WM, and 
see if that works.  Also it gives something definite to go on, and I can take 
it to the Fluxbox list.  A pity because I've found Fluxbox just about perfect.  
Obviously its not for everyone.

Thanks again for the suggestions.

Peter


On Wed, 01 Nov 2023 09:52:08 +
lyx-users-requ...@lists.lyx.org wrote:

> Send lyx-users mailing list submissions to
>   lyx-users@lists.lyx.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   http://lists.lyx.org/mailman/listinfo/lyx-users
> or, via email, send a message with subject or body 'help' to
>   lyx-users-requ...@lists.lyx.org
> 
> You can reach the person managing the list at
>   lyx-users-ow...@lists.lyx.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lyx-users digest..."
> 
> 
> Today's Topics:
> 
>1. Re: Debian 12 and Lyx 2.3.7-1 (Folsk Pratima)
>2. Re: Debian 12 and Lyx 2.3.7-1 (Folsk Pratima)
>3. Re: Debian 12 and Lyx 2.3.7-1 (Peter)
>4. Re: Debian 12 and Lyx 2.3.7-1 (Folsk Pratima)
> 
> 
> --
> 
> Message: 1
> Date: Wed, 1 Nov 2023 10:22:54 +0200
> From: Folsk Pratima 
> To: lyx-users@lists.lyx.org
> Subject: Re: Debian 12 and Lyx 2.3.7-1
> Message-ID: <20231101102254.69039...@void.wired-node-303707.moe>
> Content-Type: text/plain; charset=US-ASCII
> 
> See here:
> http://lists.lyx.org/pipermail/lyx-users/2023-November/005981.html
> 
> Something went wrong and I created a new thread...
> 
> 
> --
> 
> Message: 2
> Date: Wed, 1 Nov 2023 10:23:48 +0200
> From: Folsk Pratima 
> To: lyx-users@lists.lyx.org
> Subject: Re: Debian 12 and Lyx 2.3.7-1
> Message-ID: <20231101102348.022a8...@void.wired-node-303707.moe>
> Content-Type: text/plain; charset=US-ASCII
> 
> :'(
> 
> 
> --
> 
> Message: 3
> Date: Wed, 1 Nov 2023 08:47:18 +
> From: Peter 
> To: "lyx-users@lists.lyx.org" 
> Subject: Re: Debian 12 and Lyx 2.3.7-1
> Message-ID: <20231101084718.64a4bde4@silverstone>
> Content-Type: text/plain; charset=US-ASCII
> 
> Thanks so much for the suggestions!
> 
> I ran (as myself) QT-DEBUG, and the same thing happened.  Blank screen, but 
> lyx was showing in the bottom fluxbox menu bar, so I quickly closed the app 
> and managed to avoid the crash, and thus was able to copy the terminal 
> output.  It was as follows.  Sorry, its very long.  It means nothing to me.  
> I'm a long time Debian user, but no sort of serious programming background.
> 
> I'll have a go with some of the other suggestions next.  I guess one obvious 
> one is to install KDE andtry it with that, since someone reports having no 
> problems with that on Debian 12.  Can always take it out afterwards.  Or 
> maybe beta 2.4.
> 
> Peter
> 
> [regular user]~$ QT_DEBUG_PLUGINS=1 lyx
> QFactoryLoader::QFactoryLoader() checking directory path 
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms" ...
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so"
> Found metadata in lib 
> /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so, metadata=
> {
> "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "eglfs"
> ]
> },
> "archreq": 0,
> "className": "QEglFSIntegrationPlugin",
> "debug": false,
> "version": 331520
> }
> 
> 
> Got keys from plugin meta data ("eglfs")
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so"
> Found metadata in lib 
> /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so, metadata=
> {
> "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "linuxfb"
> ]
> },
> "archreq": 0,
> "className": "QLinuxFbIntegrationPlugin",
> "debug": false,
> "version": 331520
> }
> 
> 
> Got keys from plugin meta data ("linuxfb")
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimal.so"
> Found metadata in lib 
> /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimal.so, metadata=
> {
> "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "minimal"
> ]
> },
> "archreq": 0,
> "className": "QMinimalIntegrationPlugin",
> "debug": false,
> "version": 331520
> }
> 
> 

Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Folsk Pratima
On Wed, 1 Nov 2023 08:47:18 +
Peter  wrote:

> QFactoryLoader::QFactoryLoader() checking directory path
> "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms" ...
> QFactoryLoader::QFactoryLoader() looking at
> ...

The irony is that your debug log is like mine minus qt5ct plus some
KIconEnginePlugin, so it does not look like there are any errors.
Except I'm not a developer as well, so I may well be wrong.
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Peter
Thanks so much for the suggestions!

I ran (as myself) QT-DEBUG, and the same thing happened.  Blank screen, but lyx 
was showing in the bottom fluxbox menu bar, so I quickly closed the app and 
managed to avoid the crash, and thus was able to copy the terminal output.  It 
was as follows.  Sorry, its very long.  It means nothing to me.  I'm a long 
time Debian user, but no sort of serious programming background.

I'll have a go with some of the other suggestions next.  I guess one obvious 
one is to install KDE andtry it with that, since someone reports having no 
problems with that on Debian 12.  Can always take it out afterwards.  Or maybe 
beta 2.4.

Peter

[regular user]~$ QT_DEBUG_PLUGINS=1 lyx
QFactoryLoader::QFactoryLoader() checking directory path 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms" ...
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqeglfs.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"eglfs"
]
},
"archreq": 0,
"className": "QEglFSIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("eglfs")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqlinuxfb.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"linuxfb"
]
},
"archreq": 0,
"className": "QLinuxFbIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("linuxfb")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimal.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimal.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"minimal"
]
},
"archreq": 0,
"className": "QMinimalIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("minimal")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimalegl.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqminimalegl.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"minimalegl"
]
},
"archreq": 0,
"className": "QMinimalEglIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("minimalegl")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqoffscreen.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqoffscreen.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"offscreen"
]
},
"archreq": 0,
"className": "QOffscreenIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("offscreen")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqvnc.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqvnc.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"vnc"
]
},
"archreq": 0,
"className": "QVncIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("vnc")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-egl.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-egl.so, metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland-egl"
]
},
"archreq": 0,
"className": "QWaylandEglPlatformIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("wayland-egl")
QFactoryLoader::QFactoryLoader() looking at 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-generic.so"
Found metadata in lib 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-generic.so, 
metadata=
{
"IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
"MetaData": {
"Keys": [
"wayland"
]
},
"archreq": 0,
"className": "QWaylandIntegrationPlugin",
"debug": false,
"version": 331520
}


Got keys from plugin meta data ("wayland")

Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Folsk Pratima
:'(
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Folsk Pratima
See here:
http://lists.lyx.org/pipermail/lyx-users/2023-November/005981.html

Something went wrong and I created a new thread...
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Folsk Pratima
Sorry, no idea why this went to a separate thread...
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-11-01 Thread Folsk Pratima
On Tue, 31 Oct 2023 09:31:13 +
Peter wrote:

> Hi, I have just upgraded to Debian 12 and find Lyx will not load.  In
> addition, trying to load it seems to crash xorg, so the only way out
> is to reboot.  I was going to post the slew of error messages from
> the terminal, but as soon as I opened Claws the display became
> unusable.  Moving the cursor led to a broad black line across the
> display, and clicking no longer worked.
> 
> I have tried starting Lyx from the terminal as a different user, and
> I get this:
> 
> [different user]:~$ lyx
> qt.qpa.xcb: could not connect to display 
> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even
> though it was found. This application failed to start because no Qt
> platform plugin could be initialized. Reinstalling the application may
> fix this problem.
> 
> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
> offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl,
> wayland-xcomposite-glx, xcb.
> 
> I have checked, and xcb is installed.
> 
> Any suggestions?  Should I try to revert to an earlier version, which
> worked just fine under Debian 11, and if so how would one do that?  I
> have tried reinstalling as suggested above, but it makes no
> difference.
> 
> What happens on launch is that a large window with no borders comes
> up.  The Lyx starting logo is in the middle.  But there is no
> toolbar, neither right nor left clicks work either.
> 
> This is Debian 12 with fluxbox. 
> 
> Any help gratefully received.  I can try running debug if anyone
> knows what flags to use and what to look for.
> 
> Peter

I did not upgrade from Debian 11, but made a clean install and Lyx
works just fine, so it is problem with your upgrade. AFAIK it is common
for X to break on Debian upgrade.

Sorry, I am not going to be much help but if you are really
desperate you could try doing something nuclear like
```
dpkg-query -f '${Package} ${db:Status-Status}\n' -W '*xorg*' -W '*gtk*'
-W '*qt*' | awk '/ installed$/'
```
and deleting all (or most) of the packages. It will be a bit of a hassle
to install them all again especially if your installation is big, but it
*might* fix you problem.

Also, a tiny bit of lurking:
https://stackoverflow.com/questions/67272188/debian-10-qt-qpa-plugin-could-not-load-the-qt-platform-plugin-xcb-in-eve
I assume it's not likely "$DISPLAY" is missing, but maybe really some
xcb libraries got deleted during upgrade? Are other qt applications
working?

You can also `apt purge lyx` and then install in again...

You can also `strace lyx > ~/tmp/trace 2>&1` and then skim trough it
after reboot, but believe me that's not going to be pretty.
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-10-31 Thread Eckhard Höffner
I have no problems on debian, but I'm using kde. Starting from the 
terminal gives no output.


It appears that lyx does not connect to the windowmanager fluxbox.


Am 31.10.23 um 10:31 schrieb Peter:

Hi, I have just upgraded to Debian 12 and find Lyx will not load.  In addition, 
trying to load it seems to crash xorg, so the only way out is to reboot.  I was 
going to post the slew of error messages from the terminal, but as soon as I 
opened Claws the display became unusable.  Moving the cursor led to a broad 
black line across the display, and clicking no longer worked.

I have tried starting Lyx from the terminal as a different user, and I get this:

[different user]:~$ lyx
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even
though it was found. This application failed to start because no Qt
platform plugin could be initialized. Reinstalling the application may
fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl,
wayland-xcomposite-glx, xcb.

I have checked, and xcb is installed.

Any suggestions?  Should I try to revert to an earlier version, which worked 
just fine under Debian 11, and if so how would one do that?  I have tried 
reinstalling as suggested above, but it makes no difference.

What happens on launch is that a large window with no borders comes up.  The 
Lyx starting logo is in the middle.  But there is no toolbar, neither right nor 
left clicks work either.

This is Debian 12 with fluxbox.

Any help gratefully received.  I can try running debug if anyone knows what 
flags to use and what to look for.

Peter
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12 and Lyx 2.3.7-1

2023-10-31 Thread Isaac Oscar Gariano

That's not good, Linux GUI problems are often very hard to debug...

I'm guessing the xcb issue might be because you are a different user, but you 
can try using "QT_DEBUG_PLUGINS=1 lyx" to
get some more information.

You said you got lots of error messages, perhaps if you run `lyx -x lyx-quit` 
lyx will survive long enough to give error messages but not long enough to 
completely crash you're computer?

You can also try using SSH and X-Forwarding to yourself with 'ssh -X localhost 
lyx' I've had to use that due to GUI problems before. But if you haven't 
already got SSH set up it's a bit involved to do so.

Do other QT applications have problems, or is it just LyX? You could also try 
the beta for 2.4 which uses Qt6 (see https://ftp.lip6.fr/pub/lyx/devel/lyx-2.4/)

From: lyx-users  on behalf of Peter 

Sent: Tuesday, 31 October 2023 10:31 PM
To: lyx-users@lists.lyx.org 
Subject: Debian 12 and Lyx 2.3.7-1

Hi, I have just upgraded to Debian 12 and find Lyx will not load.  In addition, 
trying to load it seems to crash xorg, so the only way out is to reboot.  I was 
going to post the slew of error messages from the terminal, but as soon as I 
opened Claws the display became unusable.  Moving the cursor led to a broad 
black line across the display, and clicking no longer worked.

I have tried starting Lyx from the terminal as a different user, and I get this:

[different user]:~$ lyx
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even
though it was found. This application failed to start because no Qt
platform plugin could be initialized. Reinstalling the application may
fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl,
wayland-xcomposite-glx, xcb.

I have checked, and xcb is installed.

Any suggestions?  Should I try to revert to an earlier version, which worked 
just fine under Debian 11, and if so how would one do that?  I have tried 
reinstalling as suggested above, but it makes no difference.

What happens on launch is that a large window with no borders comes up.  The 
Lyx starting logo is in the middle.  But there is no toolbar, neither right nor 
left clicks work either.

This is Debian 12 with fluxbox.

Any help gratefully received.  I can try running debug if anyone knows what 
flags to use and what to look for.

Peter
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Debian 12 and Lyx 2.3.7-1

2023-10-31 Thread Peter
Hi, I have just upgraded to Debian 12 and find Lyx will not load.  In addition, 
trying to load it seems to crash xorg, so the only way out is to reboot.  I was 
going to post the slew of error messages from the terminal, but as soon as I 
opened Claws the display became unusable.  Moving the cursor led to a broad 
black line across the display, and clicking no longer worked.

I have tried starting Lyx from the terminal as a different user, and I get this:

[different user]:~$ lyx
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even
though it was found. This application failed to start because no Qt
platform plugin could be initialized. Reinstalling the application may
fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl,
wayland-xcomposite-glx, xcb.

I have checked, and xcb is installed.

Any suggestions?  Should I try to revert to an earlier version, which worked 
just fine under Debian 11, and if so how would one do that?  I have tried 
reinstalling as suggested above, but it makes no difference.

What happens on launch is that a large window with no borders comes up.  The 
Lyx starting logo is in the middle.  But there is no toolbar, neither right nor 
left clicks work either.

This is Debian 12 with fluxbox. 

Any help gratefully received.  I can try running debug if anyone knows what 
flags to use and what to look for.

Peter
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12

2023-10-27 Thread John White
Me too (using Debian for more than 20 years).  My lyx problem is new and 
surfaced after we upgraded to Debian 12.  However I am not sure the upgrade 
had anything to do with it.

On Friday, October 27, 2023 2:43:22 AM PDT Eckhard Höffner wrote:
> There are methods, to install both (use your home or /usr/local).  The
> system will prefer your home or /usr/local installation.  However, on
> debian, you can install texlive-full and you will get everything,
> including all the language, fonts, format and other files you'll never
> need,
> 
> In general, there are no issues with debian, and I am using it for more
> than twenty years.
> 
> Am 27.10.23 um 07:24 schrieb Steve Litt:
> > John White said on Thu, 26 Oct 2023 09:02:44 -0700
> > 
> >> We recently updated the three computers used by staff to Debian 12.
> >> My computer is still Debian 11.
> > 
> > My personal opinion is it's much better to install texlive from the TUG
> > website rather than from your distro, because you can get everything
> > related to texlive at the TUG website. And whatever you do, never, EVER
> > install texlive from both TUG and your distro.
> > 
> > SteveT
> > 
> > Steve Litt
> > 
> > Autumn 2023 featured book: Rapid Learning for the 21st Century
> > http://www.troubleshooters.com/rl21



-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Setting default document class

2023-10-27 Thread Paul Rubin




On 10/26/23 13:13, Rich Shepard wrote:



Speaking of which, if you go to ~/.lyx/templates, you should see a file
named defaults.lyx. That's your default starting document. All else
failing, try creating an empty doc with the Report class, saving it to
/tmp with the name defaults.lyx, and then moving it over to the 
templates

directory.


Okay. I didn't look in templates, but there the textclass is set to
scrreport so I cannot explain why a new doc comes up as scrbook.

Oh, well. I'll cope with it. :-)

Many thanks,

Rich
You might try "grep template_path ~/.lyx/preferences" and make sure that 
your template directory is correctly set (~/.lyx/templates). If LyX is 
looking for templates in the wrong place, that might explain why it's 
defaulting to the wrong class.


You sure know how to have fun!

Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: LyX 2.3.7 & BibLaTeX?

2023-10-27 Thread Rich Shepard

On Fri, 27 Oct 2023, Bernt Lie via lyx-users wrote:


While I'm waiting, I'm starting to use Zotero to manage bibliography
files, and had some help from a more IT knowledgeable colleague. He set up
Zotero to store bibliography files as BibLaTeX. Some experience:



 1. In the past, I have used the AGSM bibliography style file. This style
doesn't seem to work with BibLaTeX?? Is there another, similar
bibliography style that works with BibLaTeX (i.e., Harvard style, etc.)??
[One change from BibTeX to BibLaTeX seems to be change of field name
"year" to field name "date"??)



 2. One *bad* (?) experience with Zotero is that it *changed* all the
bibliography *label* names. I assume this means that all past LyX/LaTeX
documents I have written will show up with *broken* references if I switch
to the new *.bib file generated by Zotero.



To repeat: my question is:



 *   Is there a BibLaTeX compatible bibliography style file with LyX 2.3.7
   that works similarly to how AGSM works?
 *   Or do I have to wait for LyX 2.4 for BibLaTeX compatibility?


Bernt,

I have been using JabREF for years so I don't know Zotero, but I'll try to
assist you.

What sort of data are your references? In my case they're all
ecological/environmental science and I use BibLaTeX (natbib-mode) as the
citation style format with Author-year format. The bibliography style is
authoryear and the bibliography generation processor is biber.

Here's a referece that might help you:

It uses natbib, with works with BibTex, but the BibLaTeX (natbib-mode) is
equivalent.

HTH,

Rich

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12

2023-10-27 Thread Rich Shepard

On Thu, 26 Oct 2023, John White wrote:


Thanks Ecljard and Rich,


John,

You're welcome.


I have forwarded your input to our IT guy and will let you know what he
says. He thinks there may be problems other than pstricks.sty. Before
calling him I loaded every texlive program available on synaptic (except
full) and reconfigured lyx and that didn't help.


Have you (or your IT techie) installed TeXLive2023 on all hosts? If not, I
recommend that you have that done, especially directly from the TUG (TeX
Users Group) web site . It has explicit
instructions for downloading and installing from the Web and that way all
hosts have the same, and most current, installation. That should resolve any
issues.

He can also periodically update the installation from the TUG web site with
a shell script in each host's /etc/cron.weekly (or the Debian equivalent).
Here (on Slackware) my script, update-tlmgr.sh, contains:
cd /usr/local/texlive/2023/bin/x86_64-linux/
./tlmgr update --self --all
./fmtutil-sys --sys -all
cd

This keeps the installation current.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12

2023-10-27 Thread Eckhard Höffner
There are methods, to install both (use your home or /usr/local).  The 
system will prefer your home or /usr/local installation.  However, on 
debian, you can install texlive-full and you will get everything, 
including all the language, fonts, format and other files you'll never 
need,


In general, there are no issues with debian, and I am using it for more 
than twenty years.



Am 27.10.23 um 07:24 schrieb Steve Litt:

John White said on Thu, 26 Oct 2023 09:02:44 -0700


We recently updated the three computers used by staff to Debian 12.
My computer is still Debian 11.

My personal opinion is it's much better to install texlive from the TUG
website rather than from your distro, because you can get everything
related to texlive at the TUG website. And whatever you do, never, EVER
install texlive from both TUG and your distro.

SteveT

Steve Litt

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


LyX 2.3.7 & BibLaTeX?

2023-10-27 Thread Bernt Lie via lyx-users
I'm on LyX 2.3.7, eagerly awaiting the release of 2.4 (whenever that will be).

While I'm waiting, I'm starting to use Zotero to manage bibliography files, and 
had some help from a more IT knowledgeable colleague. He set up Zotero to store 
bibliography files as BibLaTeX. Some experience:


  1.  In the past, I have used the AGSM bibliography style file. This style 
doesn't seem to work with BibLaTeX?? Is there another, similar bibliography 
style that works with BibLaTeX (i.e., Harvard style, etc.)?? [One change from 
BibTeX to BibLaTeX seems to be change of field name "year" to field name 
"date"??)
  2.  One *bad* (?) experience with Zotero is that it *changed* all the 
bibliography *label* names. I assume this means that all past LyX/LaTeX 
documents I have written will show up with *broken* references if I switch to 
the new *.bib file generated by Zotero.

To repeat: my question is:

  *   Is there a BibLaTeX compatible bibliography style file with LyX 2.3.7 
that works similarly to how AGSM works?
  *   Or do I have to wait for LyX 2.4 for BibLaTeX compatibility?

Thanks,
BL

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12

2023-10-26 Thread Steve Litt
John White said on Thu, 26 Oct 2023 09:02:44 -0700

>We recently updated the three computers used by staff to Debian 12.
>My computer is still Debian 11.  

My personal opinion is it's much better to install texlive from the TUG
website rather than from your distro, because you can get everything
related to texlive at the TUG website. And whatever you do, never, EVER
install texlive from both TUG and your distro.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12

2023-10-26 Thread John White
Thanks Ecljard and Rich,

I have forwarded your input to our IT guy and will let you know what he says. 
He thinks there may be problems other than pstricks.sty. Before calling him I 
loaded every texlive program available on synaptic (except full) and 
reconfigured lyx and that didn't help.

John

On Thursday, October 26, 2023 10:21:26 AM PDT Eckhard Höffner wrote:
> Well, the file is here:
> 
> kpsewhich pstricks.sty
> 
> /usr/share/texlive/texmf-dist/tes/latex/pstricks
> 
> and part of the package texlive-pstricks.
> 
> If the package is installed, there must be another problem.
> 
> Am 26.10.23 um 18:02 schrieb John White:
> > We recently updated the three computers used by staff to Debian 12.  My
> > computer is still Debian 11.
> > 
> > Though mine still works fine, none of the updated computers will generate
> > pdfs. They all show an error to the effect that it can't find
> > pstricks.sty.
> > 
> > Our IT guy is here now trying to fix it but I thought a quick email to
> > this
> > site might produce some helpful comments.
> > 
> > John



-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Easiest to read page size

2023-10-26 Thread Rich Shepard

On Thu, 26 Oct 2023, Steve Litt wrote:


The fact that you're using double sided printing indicates to me that your
expected output format is paper.


Steve,

I thought that I made that point. Regardless, ...


I presume your choice of page size is done based on what book sizes can be
done for what price.


This is a tech report to an environmental regulator that I expect to be
presented to a state legislator for assistance. :-)

I don't know how old the regulatory agency staffer is, but I know the
process will be difficult.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Easiest to read page size

2023-10-26 Thread Steve Litt
Rich Shepard said on Thu, 26 Oct 2023 12:59:21 -0700 (PDT)

>On Thu, 26 Oct 2023, Steve Litt wrote:
>
>> I've done some research on this topic. Generally speaking, each line
>> should be a little less than 70 characters. If they get much longer,
>> the reader has a hard time going to the proper next line. If they
>> get much shorter, you get increases hyphenation and funky inter-word
>> spacing.  
>
>Steve,
>
>That's consistent with what I read years ago when I consumed several
>books on typography.
>
>> Beyond that, a lot of readability hinges on where the reader will be
>> reading. Paper? PDF on full sized monitor? PDF on mobile device?
>> ePub? Combination of preceding?  
>
>The document is a PDF. I've set the page size to US Executive
>(8"x10"), text font is URW Palatino 11 pt. Outer margins are 0.5",
>inner margins 0.9" for binding (it's typeset for double-side printing.)
>
>If someone wants to read it on their mobile telephone, wristwatch, or
>eyeglasses it's up to them to do so.
>
>Thanks,

Hi Rich,

The fact that you're using double sided printing indicates to me that
your expected output format is paper. If the binding is at all stiff,
0.9" seems like too short an inside margin to me. 11pt is nice, but it
makes for some problems for those whose vision isn't correctable to
20/20. For those reasons I use 12pt or 14pt, but of course if you
expect your readership to be primarily young, 11pt is good. 11pt
would save a lot of printing cost compared to 12pt. I'm glad you didn't
choose 10pt.

I presume your choice of page size is done based on what book sizes can
be done for what price.

Bringing out a new book is always exciting.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Easiest to read page size

2023-10-26 Thread Rich Shepard

On Thu, 26 Oct 2023, Steve Litt wrote:


I've done some research on this topic. Generally speaking, each line
should be a little less than 70 characters. If they get much longer, the
reader has a hard time going to the proper next line. If they get much
shorter, you get increases hyphenation and funky inter-word spacing.


Steve,

That's consistent with what I read years ago when I consumed several books
on typography.


Beyond that, a lot of readability hinges on where the reader will be
reading. Paper? PDF on full sized monitor? PDF on mobile device? ePub?
Combination of preceding?


The document is a PDF. I've set the page size to US Executive (8"x10"), text
font is URW Palatino 11 pt. Outer margins are 0.5", inner margins 0.9" for
binding (it's typeset for double-side printing.)

If someone wants to read it on their mobile telephone, wristwatch, or
eyeglasses it's up to them to do so.

Thanks,

Rich


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Easiest to read page size

2023-10-26 Thread Steve Litt
Rich Shepard said on Wed, 25 Oct 2023 10:36:55 -0700 (PDT)

>My web searches for the optimal printed document page size finds only
>hits on fonts, not the page size itself. I'm curious whether an
>executive page size (8x10 inches) would be more readable than the
>letter page size (8.5x11 inches) because each text line is shorter. If
>shorter text lines read more quickly then perhaps 6x9 inches would be
>a good page size.
>
>Those with more knowledge on page size and readability are encouraged
>to share their knowledge with me.

Hi Rich,

I've done some research on this topic. Generally speaking, each line
should be a little less than 70 characters. If they get much longer,
the reader has a hard time going to the proper next line. If they get
much shorter, you get increases hyphenation and funky inter-word
spacing.

Beyond that, a lot of readability hinges on where the reader will be
reading. Paper? PDF on full sized monitor? PDF on mobile device? ePub?
Combination of preceding?

By the way Rich, if it ends up that you need a custom size, let's say 5
inches high and 3 inches wide to fit a mobile device, I can help you
with that, as I'm already doing it. My method works for the standard
book document class; you can translate it into KOMA, which I believe is
your document class of choice.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12

2023-10-26 Thread Eckhard Höffner

Well, the file is here:

kpsewhich pstricks.sty

/usr/share/texlive/texmf-dist/tes/latex/pstricks

and part of the package texlive-pstricks.

If the package is installed, there must be another problem.



Am 26.10.23 um 18:02 schrieb John White:

We recently updated the three computers used by staff to Debian 12.  My
computer is still Debian 11.

Though mine still works fine, none of the updated computers will generate pdfs.
They all show an error to the effect that it can't find pstricks.sty.

Our IT guy is here now trying to fix it but I thought a quick email to this
site might produce some helpful comments.

John



--
Eckhard Höffner
Volkarstr. 64
D-80636 München
Tel.: 089 210 31 888
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Debian 12

2023-10-26 Thread Rich Shepard

On Thu, 26 Oct 2023, John White wrote:


We recently updated the three computers used by staff to Debian 12.  My
computer is still Debian 11.

Though mine still works fine, none of the updated computers will generate pdfs.
They all show an error to the effect that it can't find pstricks.sty.

Our IT guy is here now trying to fix it but I thought a quick email to this
site might produce some helpful comments.


John,

Have you tried searching (using 'locate' or 'whereis') for pstricks.sty on
the Debian 12 hosts?

How often do you use PSTricks' graphics in a legal document?

Regards,

Rich

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Setting default document class

2023-10-26 Thread Rich Shepard

On Thu, 26 Oct 2023, Paul Rubin wrote:

Are you saying that the doc class within a document kept changing back to 
Book on its own, or that the default class kept changing back to Book?


Paul,

Yes, the doc class changed back to Book a couple of times, but that's the
only time I've seen this happen. I can't explain it either.


Speaking of which, if you go to ~/.lyx/templates, you should see a file
named defaults.lyx. That's your default starting document. All else
failing, try creating an empty doc with the Report class, saving it to
/tmp with the name defaults.lyx, and then moving it over to the templates
directory.


Okay. I didn't look in templates, but there the textclass is set to
scrreport so I cannot explain why a new doc comes up as scrbook.

Oh, well. I'll cope with it. :-)

Many thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Setting default document class

2023-10-26 Thread Paul Rubin




On 10/26/23 11:54, Rich Shepard wrote:

On Thu, 26 Oct 2023, Paul Rubin wrote:

Create a new document, select the document class you want as default, 
and

make any other customizations that you want applied to new documents
(fonts, paper size, whatever). Then go to Document > Settings... >
Document Class and click "Save as Document Defaults".


Paul,

Sigh. Yes, I did that yesterday with a new document. The default when the
new doc opened was KOMA-Script Book. I changed it to KOMA-Script 
Report and
clicked the link, "Save as Document Class." (Aside, it kept shifting 
back to

Book and I kept changing that to Report.)

Now, starting a new doc the default class is "KOMA-Script Book" which 
is why
I thought there might be another place that actually set the default 
class I

want.

Thanks,

Rich


Rich,

Are you saying that the doc class within a document kept changing back 
to Book on its own, or that the default class kept changing back to 
Book? I would have no explanation for the former. The latter might 
indicate a permissions problem with the directory where the default is 
saved.


Speaking of which, if you go to ~/.lyx/templates, you should see a file 
named defaults.lyx. That's your default starting document. All else 
failing, try creating an empty doc with the Report class, saving it to 
/tmp with the name defaults.lyx, and then moving it over to the 
templates directory.


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Debian 12

2023-10-26 Thread John White
We recently updated the three computers used by staff to Debian 12.  My 
computer is still Debian 11.  

Though mine still works fine, none of the updated computers will generate pdfs. 
 
They all show an error to the effect that it can't find pstricks.sty.

Our IT guy is here now trying to fix it but I thought a quick email to this 
site might produce some helpful comments.

John


-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Setting default document class

2023-10-26 Thread Rich Shepard

On Thu, 26 Oct 2023, Paul Rubin wrote:


Create a new document, select the document class you want as default, and
make any other customizations that you want applied to new documents
(fonts, paper size, whatever). Then go to Document > Settings... >
Document Class and click "Save as Document Defaults".


Paul,

Sigh. Yes, I did that yesterday with a new document. The default when the
new doc opened was KOMA-Script Book. I changed it to KOMA-Script Report and
clicked the link, "Save as Document Class." (Aside, it kept shifting back to
Book and I kept changing that to Report.)

Now, starting a new doc the default class is "KOMA-Script Book" which is why
I thought there might be another place that actually set the default class I
want.

Thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Setting default document class

2023-10-26 Thread Paul Rubin



On 10/26/23 11:00, Rich Shepard wrote:

Looking in ~/.lyx/lyxrc and ../preferences I do not see where I can set a
default document class when I create a new doc. Have I missed seeing 
where I

can do this?

TIA,

Rich
Create a new document, select the document class you want as default, 
and make any other customizations that you want applied to new documents 
(fonts, paper size, whatever). Then go to Document > Settings... > 
Document Class and click "Save as Document Defaults".


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Setting default document class

2023-10-26 Thread Rich Shepard

Looking in ~/.lyx/lyxrc and ../preferences I do not see where I can set a
default document class when I create a new doc. Have I missed seeing where I
can do this?

TIA,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Easiest to read page size

2023-10-25 Thread Eckhard Höffner
This is a question that cannot be answered as such. If you have a large 
font, the page size will generally be larger too. The usual font size 
for American science paperbacks is 9 x 6 inches and 11 pt.In general, up 
to 65 letters (including spaces) are legible; but there can be 80. If 
the line spacing is large, the page can also be larger because more 
letters can fit into one line.





Am 25.10.23 um 19:36 schrieb Rich Shepard:
My web searches for the optimal printed document page size finds only 
hits

on fonts, not the page size itself. I'm curious whether an executive page
size (8x10 inches) would be more readable than the letter page size 
(8.5x11
inches) because each text line is shorter. If shorter text lines read 
more

quickly then perhaps 6x9 inches would be a good page size.

Those with more knowledge on page size and readability are encouraged to
share their knowledge with me.

TIA,

Rich
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Easiest to read page size

2023-10-25 Thread Rich Shepard

My web searches for the optimal printed document page size finds only hits
on fonts, not the page size itself. I'm curious whether an executive page
size (8x10 inches) would be more readable than the letter page size (8.5x11
inches) because each text line is shorter. If shorter text lines read more
quickly then perhaps 6x9 inches would be a good page size.

Those with more knowledge on page size and readability are encouraged to
share their knowledge with me.

TIA,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: bibex/arXiv

2023-10-25 Thread Richard Kimberly Heck

On 10/25/23 05:13, Patrick Dupre wrote:

Thank Richard,

Can I have a template?


You have quite a few on your system already. The bibtex ones are *.bst. 
The biblatex ones are *.bbx. Although I have not used it, I'd suggest 
you try biblatex. It is designed to be much easier to customize. "Good 
working knowledge in LaTeX should be sufficient to design new 
bibliography and citation styles", or so says the manual. The language 
used in bibtex files is a very primitive stack-based language and is not 
easy to work with, though I did manage to write a custom bst file a 
while ago.


Riki



On 10/24/23 05:20, Patrick Dupre via lyx-users wrote:

Hello,

In my bib file, I have

@ARTICLE{javaloyes03b,
AUTHOR = {J.~Javaloyes and M.~Perrin and G.L. Lippi and A.~Politi},
TITLE = {Recoil-induced lasing},
YEAR = 2003,
EPRINT = {physics/0311132},
archivePrefix = {arXiv},
primaryClass = {physics.optics},
DOI = {10.48550/arXiv.physics/0311132},
NOTE = {}
}

How can I make it come in my Bibliography section with all the information

EPRINT
archivePrefix

How this is presented in your bibliography is determined by the bibtex
or biblatex that you are using. I don't know if there's an existing
style that uses these fields. If not, you'd have to write your own.

Riki





--

Richard Kimberly (Riki) Heck
Brown University
Professor of Philosophy and Professor of Linguistics
Director of Graduate Studies in Philosophy

Office Hours: Monday 2-3, Wednesday 11-12
Personal link: https://brown.zoom.us/my/rikiheck
Pronouns: they/them/their

Email:   rikih...@brown.edu
Website: http://rkheck.frege.org/
Google Scholar:  https://scholar.google.com/citations?user=QUKBG6EJ
ORCID:   http://orcid.org/-0002-2961-2663

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: KOMA-Script Report Class: cannot select biblatex [RESOLVED]

2023-10-25 Thread Rich Shepard

On Tue, 24 Oct 2023, Paul Rubin wrote:


The Natbibapa module may be the culprit. If I remove it, I can change the
bibliography style.


Paul,

Well, shame on me! I looked at Settings and missed Modules. That's exactly
the cause. How that module was added I've no idea.

Many thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: bibex/arXiv

2023-10-25 Thread Patrick Dupre via lyx-users
Thank Richard,

Can I have a template?

Thanks.

>
> On 10/24/23 05:20, Patrick Dupre via lyx-users wrote:
> > Hello,
> >
> > In my bib file, I have
> >
> > @ARTICLE{javaloyes03b,
> >AUTHOR = {J.~Javaloyes and M.~Perrin and G.L. Lippi and A.~Politi},
> >TITLE = {Recoil-induced lasing},
> >YEAR = 2003,
> >EPRINT = {physics/0311132},
> >archivePrefix = {arXiv},
> >primaryClass = {physics.optics},
> >DOI = {10.48550/arXiv.physics/0311132},
> >NOTE = {}
> >}
> >
> > How can I make it come in my Bibliography section with all the information
> >
> > EPRINT
> > archivePrefix
>
> How this is presented in your bibliography is determined by the bibtex
> or biblatex that you are using. I don't know if there's an existing
> style that uses these fields. If not, you'd have to write your own.
>
> Riki
>
>
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: KOMA-Script Report Class: cannot select biblatex

2023-10-25 Thread Dr Eberhard W Lisse
So it was not really a MWE.

el


On 2023-10-25 04:52, Paul Rubin wrote:
> On 10/24/23 14:57, Rich Shepard wrote:
[...]
>> I've created a new KOMA-Script report class MWE (attached.)  It
>> has only a title and the question, "Why can't I change the
>> bibliograpy style format in Document -> Settings ->
>> Bibliography?"
[...]
> The Natbibapa module may be the culprit.  If I remove it, I can
> change the bibliography style.
> 
> Paul

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: bibex/arXiv

2023-10-24 Thread Richard Kimberly Heck

On 10/24/23 05:20, Patrick Dupre via lyx-users wrote:

Hello,

In my bib file, I have

@ARTICLE{javaloyes03b,
   AUTHOR = {J.~Javaloyes and M.~Perrin and G.L. Lippi and A.~Politi},
   TITLE = {Recoil-induced lasing},
   YEAR = 2003,
   EPRINT = {physics/0311132},
   archivePrefix = {arXiv},
   primaryClass = {physics.optics},
   DOI = {10.48550/arXiv.physics/0311132},
   NOTE = {}
   }

How can I make it come in my Bibliography section with all the information

EPRINT
archivePrefix


How this is presented in your bibliography is determined by the bibtex 
or biblatex that you are using. I don't know if there's an existing 
style that uses these fields. If not, you'd have to write your own.


Riki


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: KOMA-Script Report Class: cannot select biblatex

2023-10-24 Thread Paul Rubin




On 10/24/23 14:57, Rich Shepard wrote:

I had a similar issue last June but there no longer are old, deprecated,
font style commands in my jabrefbib.bib file. I searched my lyx mail file
(from 2005) without seeing this particular situation.

I've created a new KOMA-Script report class MWE (attached.) It has only a
title and the question, "Why can't I change the bibliograpy style 
format in

Document -> Settings -> Bibliography?"

The style format data entry box has greyed out 'Natbib (BibTex)' and 
there

are no other choices available.

What do I do to fix this so I can select BibLaTeX as the style format 
(and

related style choices?)

TIA,

Rich

The Natbibapa module may be the culprit. If I remove it, I can change 
the bibliography style.


Paul
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


KOMA-Script Report Class: cannot select biblatex

2023-10-24 Thread Rich Shepard

I had a similar issue last June but there no longer are old, deprecated,
font style commands in my jabrefbib.bib file. I searched my lyx mail file
(from 2005) without seeing this particular situation.

I've created a new KOMA-Script report class MWE (attached.) It has only a
title and the question, "Why can't I change the bibliograpy style format in
Document -> Settings -> Bibliography?"

The style format data entry box has greyed out 'Natbib (BibTex)' and there
are no other choices available.

What do I do to fix this so I can select BibLaTeX as the style format (and
related style choices?)

TIA,

Rich
#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 544
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass scrreprt
\begin_preamble
\date{}
\usepackage{mathpazo,amssymb}
\usepackage{graphicx,relsize}
\usepackage{scrlayer-scrpage}
\pagestyle{scrheadings}
\makeatletter
\@addtoreset{figure}{subsection}% Reset figure numbering at every part
\makeatother
\end_preamble
\use_default_options false
\begin_modules
natbibapa
\end_modules
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding default
\fontencoding global
\font_roman "palatino" "default"
\font_sans "avant" "default"
\font_typewriter "courier" "default"
\font_math "auto" "auto"
\font_default_family rmdefault
\use_non_tex_fonts false
\font_sc true
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\use_microtype false
\use_dash_ligatures false
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command biber
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize custom
\use_geometry true
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 0
\use_package esint 0
\use_package mathdots 1
\use_package mathtools 0
\use_package mhchem 1
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine natbib
\cite_engine_type authoryear
\biblio_style authordate4
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\use_minted 0
\index Index
\shortcut idx
\color #008000
\end_index
\paperwidth 6in
\paperheight 9in
\leftmargin 0.75in
\topmargin 0.9in
\rightmargin 0.75in
\bottommargin 0.9in
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\is_math_indent 0
\math_numbering_side default
\quotes_style english
\dynamic_quotes 0
\papercolumns 1
\papersides 2
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Title
Minimal Wrong Example: KOMA-Script Report Class Bibliography
\end_layout

\begin_layout Standard
Why can't I change the style format to biblatex?
\end_layout

\end_body
\end_document
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


bibex/arXiv

2023-10-24 Thread Patrick Dupre via lyx-users
Hello,

In my bib file, I have

@ARTICLE{javaloyes03b,
  AUTHOR = {J.~Javaloyes and M.~Perrin and G.L. Lippi and A.~Politi},
  TITLE = {Recoil-induced lasing},
  YEAR = 2003,
  EPRINT = {physics/0311132},
  archivePrefix = {arXiv},
  primaryClass = {physics.optics},
  DOI = {10.48550/arXiv.physics/0311132},
  NOTE = {}
  }

How can I make it come in my Bibliography section with all the information

EPRINT
archivePrefix

DOI

Thanks

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
===

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding standard enviroment text in a list

2023-10-20 Thread Rich Shepard

On Thu, 19 Oct 2023, Steve Litt wrote:


No problem. In your window manager or desktop or whatever, link an unused
key combo to the proper screenshot command. Or just install dmenu and run
the proper screenshot command from there.


SteveT,

Since the enumitem package did not offer any options I used what I had done
before: the issues to be addressed are in the paragraph environment and the
responses are in the subparagraph environment. That distinguishes them.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding standard enviroment text in a list

2023-10-19 Thread Steve Litt
Rich Shepard said on Thu, 19 Oct 2023 11:39:46 -0700 (PDT)

>I cannot grab a screen shot because
>moving off the LyX window to take a shot closes the right-click dialog
>box.

No problem. In your window manager or desktop or whatever, link an
unused key combo to the proper screenshot command. Or just install
dmenu and run the proper screenshot command from there.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding bibliography to ToC

2023-10-19 Thread Rich Shepard

On Thu, 19 Oct 2023, Joel Kulesza wrote:


Do you have an MWE?


Joel,

No. I restored the unmodified copy from Tuesday's backup and added the
bibliography. Comparing the Settings -> Bibliography with a document having
no build issues I found that the new doc did not contain the biber processor
selected (it was the default) and it lacked the processor option of
mergedate=compact.

That fixed the problem and I completely forgot about posting the fix on the
mail list.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding bibliography to ToC

2023-10-19 Thread Joel Kulesza
Rich,

Do you have an MWE?

Thanks,
Joel

On Thu, Oct 19, 2023 at 10:41 Rich Shepard  wrote:

> When I added the bibliography to the document I checked the box to have it
> added to the ToC. But it's not shown. What might I have missed?
>
> TIA,
>
> Rich
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding standard enviroment text in a list

2023-10-19 Thread Herbert Voss



Am 19.10.23 um 20:39 schrieb Rich Shepard:

On Thu, 19 Oct 2023, Herbert Voss wrote:


Load the module enumitem (docuemnt->settings->modules).
- Then start a enumerate paragraph and insert Text
- Choose default paragraph style which ends the enumeration.
   Insert your text which appears outside the enmeration.
- Choose again the enumerate paragraph style and click with _right_
  mouse button and insert for enumeration option s "resume"
  Insert now the text for the enumeration text.


Herbert,

Steps 1 and 2 work, but when I right-click on the next enumerated item
there's no option entry offered. I cannot grab a screen shot because 
moving

off the LyX window to take a shot closes the right-click dialog box.


Maybe a problem with LyX 2.3, because I habe 2.4. beta

Herbert-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding standard enviroment text in a list

2023-10-19 Thread Rich Shepard

On Thu, 19 Oct 2023, Herbert Voss wrote:


Load the module enumitem (docuemnt->settings->modules).
- Then start a enumerate paragraph and insert Text
- Choose default paragraph style which ends the enumeration.
   Insert your text which appears outside the enmeration.
- Choose again the enumerate paragraph style and click with _right_
  mouse button and insert for enumeration option s "resume"
  Insert now the text for the enumeration text.


Herbert,

Steps 1 and 2 work, but when I right-click on the next enumerated item
there's no option entry offered. I cannot grab a screen shot because moving
off the LyX window to take a shot closes the right-click dialog box.

Thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding standard enviroment text in a list

2023-10-19 Thread Herbert Voss




Am 19.10.23 um 20:29 schrieb Rich Shepard:

On Thu, 19 Oct 2023, Rich Shepard wrote:


Looks like a really kool solution. Would this work in LyX, too?


I added the new environment to the prefix (at the end), reconfigured LyX,
and restarted it. There's no Normanlize in the environment list.


Rich,
you do not need the special environment. Simply using the option
"resume" is enough. Then the counter doesn't restart. Try it as
I wrote in my mail.

Herbert

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding standard enviroment text in a list

2023-10-19 Thread Rich Shepard

On Thu, 19 Oct 2023, Rich Shepard wrote:


Looks like a really kool solution. Would this work in LyX, too?


I added the new environment to the prefix (at the end), reconfigured LyX,
and restarted it. There's no Normanlize in the environment list.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Integral sign

2023-10-19 Thread Herbert Voss




Am 19.10.23 um 18:58 schrieb Folsk Pratima:

On Tue, 17 Oct 2023 09:29:41 +0200
Herbert Voss  wrote:


If you want this style also for the inline mode then write as first
math command \displaymath

Are you sure it's '\displaymath'? The thing does not work for me out of
the box. Maybe you meant '\displaystyle'?


Ah yes, youre right!

Herbert


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Adding standard enviroment text in a list

2023-10-19 Thread Herbert Voss



Am 19.10.23 um 19:30 schrieb Rich Shepard:

I have a long list of criteria (and sub-criteria) that I have in an
enumerate environment so all criteria align properly.

Each criterion needs a statement of compliance which would be in the
standard environment. When I tried to do this the enumerated list 
below was

renumbered starting with '1'.

I found a solution (adding a 'normalize' environment) using LaTeX 
external

to LyX:
. 



Looks like a really kool solution. Would this work in LyX, too?


Load the module enumitem (docuemnt->settings->modules).
- Then start a enumerate paragraph and insert Text
- Choose default paragraph style which ends the enumeration.
   Insert your text which appears outside the enmeration.
- Choose again the enumerate paragraph style and click with _right_
  mouse button and insert for enumeration option s "resume"
  Insert now the text for the enumeration text.

Inside Lyx you still see
1. lklklkllk
dsgfjhsdgljhagsdlfg
1. ölkököllö
2. jkhkjhkjh


but the LaTeX output shows:

1. lklklkllk
dsgfjhsdgljhagsdlfg
2. ölkököllö
3. jkhkjhkjh


Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Adding standard enviroment text in a list

2023-10-19 Thread Rich Shepard

I have a long list of criteria (and sub-criteria) that I have in an
enumerate environment so all criteria align properly.

Each criterion needs a statement of compliance which would be in the
standard environment. When I tried to do this the enumerated list below was
renumbered starting with '1'.

I found a solution (adding a 'normalize' environment) using LaTeX external
to LyX:
.

Looks like a really kool solution. Would this work in LyX, too?

TIA,

Rich

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Integral sign

2023-10-19 Thread Folsk Pratima
On Tue, 17 Oct 2023 09:29:41 +0200
Herbert Voss  wrote:

> If you want this style also for the inline mode then write as first
> math command \displaymath

Are you sure it's '\displaymath'? The thing does not work for me out of
the box. Maybe you meant '\displaystyle'?
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Adding bibliography to ToC

2023-10-19 Thread Rich Shepard

When I added the bibliography to the document I checked the box to have it
added to the ToC. But it's not shown. What might I have missed?

TIA,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Using LyX as merge tool for git

2023-10-18 Thread Pavel Sanda
On Tue, Oct 17, 2023 at 02:36:27PM +0200, Markus Oppmann wrote:
> Thank you for pointing me at command-sequence LFUN. I tried to automate it
> with command-sequence of comparing, then executing save as (buffer-write-as)
> but it didn't work. probably because the comparison is asynchronous, the
> buffer-write-as fails, logging that no document was open.
> 
> A parameter for the destination file name would be a great thing.

Feel free to add new bug, attempt on a patch would be even better :)

Pavel
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Using LyX as merge tool for git

2023-10-17 Thread Markus Oppmann
Am 17.10.2023 um 10:16 schrieb Pavel Sanda:>> When finished, you need to 
override the conflicted file with the generated

changes1.lyx file, close the LyX window and confirm to git that the merge
was successful.


I think it would be quite easy to enhance our lfuns, so this last "override
the conflicted file with the generated changes1.lyx file" is also automatic.
Maybe it's possible even now with command-sequence lfun?


Thank you for pointing me at command-sequence LFUN. I tried to automate 
it with command-sequence of comparing, then executing save as 
(buffer-write-as) but it didn't work. probably because the comparison is 
asynchronous, the buffer-write-as fails, logging that no document was open.


A parameter for the destination file name would be a great thing.

I am happy to create an account for you if there is an interest.


Yes, definitely. You may use my name as username. Maybe it's easiest if 
you set a temporary password and email it to me (i suppose there is a 
possibility to change your password in TRAC).



BTW beware that comparison function in LyX is not without issues:
https://www.lyx.org/trac/ticket/9395
https://www.lyx.org/trac/ticket/9048
https://www.lyx.org/trac/ticket/6889


Yes, already read that it's not perfect. Will add a hint when including 
the instructions into the Wiki.

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Header does not appear

2023-10-17 Thread Kornel Benko
Am Sun, 15 Oct 2023 21:23:40 +0200
schrieb Harold Mouras via lyx-users :

> Thank you very much for your response. The image is attached. Yes it works 
> for me but
> the « Bonjour » text is hidden by the picture. How to set up that ? 
> Thanks, 
> Harold

Works here with lyx2.4 and also with lyx2.3. Text is not hidden.

Kornel


pgpTDvlf5JXIU.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Using LyX as merge tool for git

2023-10-17 Thread Pavel Sanda
On Sun, Oct 15, 2023 at 08:27:44PM +0200, Markus Oppmann wrote:
> Just wanted to share with you how it's possible to use the compare feature
> of LyX to resolve git merge conflicts by registering LyX as a merge tool for
> git:

Interesting indeed.

> When finished, you need to override the conflicted file with the generated
> changes1.lyx file, close the LyX window and confirm to git that the merge
> was successful.

I think it would be quite easy to enhance our lfuns, so this last "override
the conflicted file with the generated changes1.lyx file" is also automatic.
Maybe it's possible even now with command-sequence lfun?

> (By the way there is bug item #8440 
> requesting such a function. Wanted to add this as comment, but i don't have
> an account in the bug tracker yet and it seems like registering is disabled)

I am happy to create an account for you if there is an interest.

> Should i write about this in the LyX Wiki? Where would be a good place for
> it? 

This one looks good... :https://wiki.lyx.org/Devel/Collaboration#toc6

BTW beware that comparison function in LyX is not without issues:
https://www.lyx.org/trac/ticket/9395
https://www.lyx.org/trac/ticket/9048
https://www.lyx.org/trac/ticket/6889

Pavel
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Integral sign

2023-10-17 Thread Herbert Voss




Am 17.10.23 um 08:21 schrieb Arshad Ali:

The integral sign written in Lyx is not looking good
image.png


That are the default symbols for the _inline_ mode (math in the text line)




as compared to other Latex packages

image.png


and that are the symbols for the _displaymode_ (math as own paragraph),
which has nothing to do with packages.

If you want this style also for the inline mode then write as first math
command \displaymath

Herbert

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Integral sign

2023-10-17 Thread Arshad Ali
The integral sign written in Lyx is not looking good
[image: image.png]
as compared to other Latex packages

[image: image.png]

is there font issue or need further development to get better.

Kindly reply

-- 

*ARSHAD ALI*
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Header does not appear

2023-10-15 Thread Harold Mouras via lyx-users
Thank you very much for your response. The image is attached. Yes it works for 
me but the « Bonjour » text is hidden by the picture.
How to set up that ? 
Thanks, 
Harold


> Le 11 oct. 2023 à 11:44, Harold Mouras  a écrit :
> 
> Hello, 
> I set up a Lyx document to be able to control the header and footpage.
> However, when compiling the pdf, the content of the header does not appear. 
> Any idea ? 
> Thanks, 
> Harold
> 

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Using LyX as merge tool for git

2023-10-15 Thread Markus Oppmann

Hi fellow LyX users,

Just wanted to share with you how it's possible to use the compare 
feature of LyX to resolve git merge conflicts by registering LyX as a 
merge tool for git:


You can add the following snippet to your ~/.gitconfig file:

For UNIX systems (should work but didn't test since i'm on Windows):

[mergetool "lyx"]
	cmd = \"/path/to/lyx" -x \"dialog-show compare run \\\"`realpath 
\"$LOCAL\"`\\\" \\\"`realpath \"$REMOTE\"`\\\"\"


and for Windows:

[mergetool "lyx"]
	cmd = \"C:\\Program Files (x86)\\LyX_2.3\\bin\\lyx\" -x \"dialog-show 
compare run \\\"`cygpath -wa \"$LOCAL\"`\\\" \\\"`cygpath -wa 
\"$REMOTE\"`\\\"\"


When you have a git-managed LyX file with merge conflicts you can then 
run "git mergetool -t lyx path/to/file.lyx" from inside the git 
repository of that file.


This should make LyX start up in compare mode and give you the ability 
to accept / reject the changes.
When finished, you need to override the conflicted file with the 
generated changes1.lyx file, close the LyX window and confirm to git 
that the merge was successful.


This strategy could maybe also be adapted to other VCS if they have the 
possibility to generate local and remote file without conflict markers.


the important part is the LyX Function to start the comparison process:

"dialog-show compare run /path/to/oldfile /path/to/newfile"

(By the way there is bug item #8440 
 requesting such a function. 
Wanted to add this as comment, but i don't have an account in the bug 
tracker yet and it seems like registering is disabled)


Should i write about this in the LyX Wiki? Where would be a good place 
for it? maybe ? or 
?


Hoping someone will find it useful.

Yours, Markus
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Don't hide menus

2023-10-13 Thread Daniel

Sorry, wrong list! Was supposed to go to the devel list.

Daniel

On 2023-10-13 08:03, Daniel wrote:
It seems to be a rather universally accepted UI rule that menu items 
should not be hidden. Feel free to can check your favorite apps or 
search the recommendation on the web. (There is also the more extreme 
recommendations to not even disable menu entries but I think it is 
generally agreed that this is a bad idea because it leaves the user 
clicking in vain.)


I am referring here foremost to the main menu items. Context-menus may 
be treated differently because they are expected to be context-dependent 
(as the name suggests).


Among the main reasons for why menu items should not be hidden are that 
with hidden menus users have a harder time


1) discovering features
2) figuring out and remembering where menu items are located

Notice that these two may be hard to appreciate for developers because 
they typically know the entries independently of whether they are shown. 
And I seem to remember a couple of instances where users were asking 
about missing features on the list which were due to OptItems being hard 
to discover.


In contrast to other applications, LyX has a greater number of menu 
entries that become hidden. I am not sure about what the history of this 
special behavior of LyX is but maybe it had to do with a trade-off in a 
time when screen size/resolution was quite limited?


I have made a test and changed all OptItems to Items in the 
stdmenus.inc. That might not show all the menu items since there are 
some whose "expansion" is hard-coded. Those expansions should typically 
have a disabled "empty" entry when there is nothing to expand. See, 
e.g., Navigate > (Empty Table of Contents) which is a perfect example of 
informing a user about a feature with a disabled entry while the feature 
is unavailable.


With this change I found that the length of the menus seemed totally 
acceptable to me (and at least not longer than for other "word 
processors").


The only exception were the various inset settings in the "Edit" menu. 
However, these seem to be mutually exclusive. So, there are different 
ways to resolve this problem. For example, to create one settings entry 
that rules them all and shows a disabled "Inset Setting..." when 
unavailable. In the short term, one might even have an exception here 
for using OptItems for this specific case.


Best,
Daniel




--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Don't hide menus

2023-10-13 Thread Daniel
It seems to be a rather universally accepted UI rule that menu items 
should not be hidden. Feel free to can check your favorite apps or 
search the recommendation on the web. (There is also the more extreme 
recommendations to not even disable menu entries but I think it is 
generally agreed that this is a bad idea because it leaves the user 
clicking in vain.)


I am referring here foremost to the main menu items. Context-menus may 
be treated differently because they are expected to be context-dependent 
(as the name suggests).


Among the main reasons for why menu items should not be hidden are that 
with hidden menus users have a harder time


1) discovering features
2) figuring out and remembering where menu items are located

Notice that these two may be hard to appreciate for developers because 
they typically know the entries independently of whether they are shown. 
And I seem to remember a couple of instances where users were asking 
about missing features on the list which were due to OptItems being hard 
to discover.


In contrast to other applications, LyX has a greater number of menu 
entries that become hidden. I am not sure about what the history of this 
special behavior of LyX is but maybe it had to do with a trade-off in a 
time when screen size/resolution was quite limited?


I have made a test and changed all OptItems to Items in the 
stdmenus.inc. That might not show all the menu items since there are 
some whose "expansion" is hard-coded. Those expansions should typically 
have a disabled "empty" entry when there is nothing to expand. See, 
e.g., Navigate > (Empty Table of Contents) which is a perfect example of 
informing a user about a feature with a disabled entry while the feature 
is unavailable.


With this change I found that the length of the menus seemed totally 
acceptable to me (and at least not longer than for other "word processors").


The only exception were the various inset settings in the "Edit" menu. 
However, these seem to be mutually exclusive. So, there are different 
ways to resolve this problem. For example, to create one settings entry 
that rules them all and shows a disabled "Inset Setting..." when 
unavailable. In the short term, one might even have an exception here 
for using OptItems for this specific case.


Best,
Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Header does not appear

2023-10-12 Thread Kornel Benko
Am Wed, 11 Oct 2023 11:11:47 -0400
schrieb Paul Rubin :

> It works for me (after I substitute an image from my computer, since 
> your image was not included). Did you check the LaTeX log for a possible 
> error message?
> 
> Paul
> 
> On 10/11/23 05:44, Harold Mouras via lyx-users wrote:
> > Hello,
> > I set up a Lyx document to be able to control the header and footpage.
> > However, when compiling the pdf, the content of the header does not appear.
> > Any idea ?
> > Thanks,
> > Harold
> >  
> 

Same here. It works.

Kornel


pgprG0KDUhA_h.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Header does not appear

2023-10-12 Thread Harold Mouras via lyx-users
Hello, I set up a Lyx document to be able to control the header and footpage.However, when compiling the pdf, the content of the header does not appear. Any idea ? Thanks, Harold

Header.lyx
Description: Binary data
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Header does not appear

2023-10-11 Thread Paul Rubin
It works for me (after I substitute an image from my computer, since 
your image was not included). Did you check the LaTeX log for a possible 
error message?


Paul

On 10/11/23 05:44, Harold Mouras via lyx-users wrote:

Hello,
I set up a Lyx document to be able to control the header and footpage.
However, when compiling the pdf, the content of the header does not appear.
Any idea ?
Thanks,
Harold



--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Header does not appear

2023-10-11 Thread Harold Mouras via lyx-users
Hello, 
I set up a Lyx document to be able to control the header and footpage.
However, when compiling the pdf, the content of the header does not appear. 
Any idea ? 
Thanks, 
Harold


Header.lyx
Description: Binary data
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


bug-report

2023-10-11 Thread Leo

Hi everybody, hope this is an ok channel to report this...

 I might have found a bug, which I described here:
https://tex.stackexchange.com/q/698031/72037

(also see my comments to the accepted answer for reproducibility)

Best,

Leo

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Line spacing in List of Figures

2023-10-10 Thread Les Denham
All,

I have a rather abstruse problem which may not have a solution, but I
would appreciate any suggestions.

I am typesetting a novel with LyX, using the Memoir Class (I am very
familiar with it), but I have come across an unusual problem. Most
novels do not have figures, but this one does. I do want a List of
Figures, but I don't want the figures numbered.

I can achieve this by removing the caption from each float and replacing
it with: 
\legend{picture name} 
\addcontentsline{lof}{figure}{picture name}

This gives the "picture name" as the caption, and in the List of
Figures at the left end of the line, with a dotted leader to the
correct page number.

The remaining problem is that the line spacing in the List of Figures
is smaller if there is more than one figure in a chapter. I would like
to have uniform line spacing in the List of Figures, regardless of
chapter breaks.

Does anyone know how to do this?

Les

-- 
Les Denham
Blizzards and Broken Grousers [typeset using LyX]
https://seg.org/shop/products/detail/237626086
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: tex2LyX error

2023-09-29 Thread Herbert Voss



Am 29.09.23 um 19:31 schrieb Hal Kierstead via lyx-users:

This took me a while because of working with two apps.

Here are a Latex file


. The Lyx file is too short. Also it does not compile because of an 
extra brace related to the equation.



The \parbox and the \label are the problem. However, a \parbox inside the
eqaution is a bit curious. You should use \text from amsmath or at least
\textit:

 \begin{equation}\label{k5y}
   k=5 \text{ and there is some } y\in N(v_1)\cap N(v_4)
   \text{ with } N_{G-C}(y)=\{z\} \text{ and } d_{G-C}(z)\ge 3.
 \end{equation}

The \label will still be the problem for tex2lyx, because it merges the
equation number (1) with the label to (1k5y).  This looks like a bug
in tex2lyx.

Herbert



--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: tex2LyX error

2023-09-29 Thread Hal Kierstead via lyx-users
Scott -

This took me a while because of working with two apps.

Here are a Latex file 

MWE.tex
Description: Binary data
and what LyX imports 

MWE.lyx
Description: Binary data
. The Lyx file is too short. Also it does not compile because of an extra brace 
related to the equation. If you erase the brace everything works. In particular 
we get the whole LyX file.

I can understand that we may get some Latex errors from the importing process, 
but why do we lose text in the LyX file?

Hal

> On Sep 29, 2023, at 8:46 AM, Scott Kostyshak  wrote:
> 
> On Fri, Sep 29, 2023 at 08:28:31AM -0700, Hal Kierstead via lyx-users wrote:
>> All - 
>> 
>> I have a 1227 line LaTeX file that compiles fine. I would like to import it 
>> into LyX 2.3.7. Every time I try the import ends at line 543. This is just 
>> before an \end{proof}. After adding the missing \end{proof} the shortened 
>> LyX file works fine. 
>> 
>> I have tried importing other LaTeX files without problems. I have also tried 
>> restarting LyX. What could be happening?
> 
> Could you please make a minimal example .tex file?
> 
> Thanks,
> Scott
> -- 
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: tex2LyX error

2023-09-29 Thread Scott Kostyshak
On Fri, Sep 29, 2023 at 08:28:31AM -0700, Hal Kierstead via lyx-users wrote:
> All - 
> 
> I have a 1227 line LaTeX file that compiles fine. I would like to import it 
> into LyX 2.3.7. Every time I try the import ends at line 543. This is just 
> before an \end{proof}. After adding the missing \end{proof} the shortened LyX 
> file works fine. 
> 
> I have tried importing other LaTeX files without problems. I have also tried 
> restarting LyX. What could be happening?

Could you please make a minimal example .tex file?

Thanks,
Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


tex2LyX error

2023-09-29 Thread Hal Kierstead via lyx-users
All - 

I have a 1227 line LaTeX file that compiles fine. I would like to import it 
into LyX 2.3.7. Every time I try the import ends at line 543. This is just 
before an \end{proof}. After adding the missing \end{proof} the shortened LyX 
file works fine. 

I have tried importing other LaTeX files without problems. I have also tried 
restarting LyX. What could be happening?

Thanks,

Hal
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Deleting outline entry

2023-09-24 Thread Daniel

On 2023-09-24 20:20, Dan via lyx-users wrote:


24 de set. de 2023, 3:25 per xraco...@gmx.de:


On 2023-09-23 21:09, Daniel wrote:


On 2023-09-23 18:50, Dan via lyx-users wrote:


Is there a way to delete an outline entry? A right-click on the entry does
not offer that option and the delete key removes characters in the
chapter/section title, not the chapter/section itself.


I do not see any way of accomplishing this via the GUI, but it can be done by 
means of the command interpreter with a pair of commands.

Say you want to delete section 2.2 of your document
    1. Place the cursor at the title of section 2.2.
    2. Issue in the command interpreter "section-select". This will select the 
whole section 2.2.
    3. To delete the entire section, then enter this command: 
"char-delete-forward". This will erase the whole section.

These steps work for any kind of sectioning (division of the text 
hierarchycally): parts, chapters, paragraphs, etc. You could even customize 
your UI file to bind these pair of commands to a button in the toolbars.



I was about to suggest to add a "Delete Section" menu entry to the TOC context 
menu. But that doesn't work for some reason and I am not sure why.

In any case, such a (working) menu entry should probably be available.

Daniel



Maybe there is some kind of cursor update missing after the "section-select" 
command?

command-sequence section-select;char-delete-forward

apparently works fine when the cursor is already in the heading but not when 
executed merely from the context-menu.

Daniel


Apparently the command "char-delete-forward" (and its twin "char-delete-backward") is 
"forbidden" in that location. Thus, adding the item
  "Delete Section|e" "command-sequence section-select; char-delete-forward"
to stdcontext.inc does not work, by design.

Try it by yourself with the debugging category "action" enabled in the messages 
pane (View > Messages Pane). Otherwise, see the debug messages attached.

It may be possible, but I do not know how.


Daniel.
--
Enviat amb Tutanota.


What works is to add a context-menu entry to the "context-edit" menu.

I don't know whether it is really by design that it does not work from 
the outline. A command being disabled is often dependent on a rather 
coarse condition. It might still be just an oversight.


In any case, it seems non-ideal that the command cannot be executed from 
the outline.


Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: updating TexLive2023: failed

2023-09-24 Thread Rich Shepard

On Sun, 24 Sep 2023, Rich Shepard wrote:


I think I need to remove /usr/share/texinfo/, /usr/share/texmf-config/,
/usr/share/texmf-dist/, /usr/share/texmf-local/, and
//usr/share/texmf-var/.


Before I FUBAR TexLive2023 I want to be certain that /usr/share/tex*/ should
be removed as redundant. Here's what I see, with only the empty
texmf-config/web2c/ having today's date:

 [root@salmo /usr/share]# ll tex*
texinfo:
total 104
drwxr-xr-x 2 root root  4096 Mar  3  2016 DebugTexinfo/
drwxr-xr-x 3 root root  4096 Mar  3  2016 Pod-Simple-Texinfo/
drwxr-xr-x 3 root root  4096 Mar  3  2016 Texinfo/
drwxr-xr-x 2 root root  4096 Feb 19  2021 html/
-rw-r--r-- 1 root root 20137 Mar  3  2016 htmlxref.cnf
drwxr-xr-x 2 root root  4096 Feb 19  2021 init/
drwxr-xr-x 5 root root  4096 Mar  3  2016 lib/
-rwxr-xr-x 1 root root 11081 Mar  3  2016 texindex.awk*
-rw-r--r-- 1 root root 45339 Mar  3  2016 texinfo.dtd

texmf-config:
total 8
-rw-r--r-- 1 root root  132 Jun 19 11:58 ls-R
drwxr-xr-x 2 root root 4096 Sep 24 05:44 web2c/

texmf-dist:
total 12
drwxr-xr-x 3 root root 4096 May 23 14:28 bibtex/
drwxr-xr-x 3 root root 4096 May 23 14:28 fonts/
-rw-r--r-- 1 root root  300 Jun 19 11:58 ls-R

texmf-local:
total 16
drwxr-xr-x 2 root root 4096 Feb  5  2020 dvips/
drwxr-xr-x 7 root root 4096 Feb  5  2020 fonts/
-rw-r--r-- 1 root root 1292 Jun 19 11:58 ls-R
drwxr-xr-x 3 root root 4096 Feb  5  2020 tex/

texmf-var:
total 16
drwxr-xr-x  3 root root 4096 Mar 24  2015 fonts/
-rw-r--r--  1 root root 3719 Jun 19 13:14 ls-R
drwxr-xr-x  3 root root 4096 Oct  3  2018 luatex-cache/
drwxr-xr-x 14 root root 4096 Jun 19 13:14 web2c/

Okay to remove these directories as they're also in
/usr/local/texlive/2023/?

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: updating TexLive2023: failed

2023-09-24 Thread Rich Shepard

On Sun, 24 Sep 2023, Herbert Voss wrote:


Does this file exists?
/usr/local/texlive/2023/texmf-dist/web2c/cp227.tcx


Herbert,

Yes:
 locate cp227.tcx
/usr/local/texlive/2023/texmf-dist/web2c/cp227.tcx


and try
pdftex -ini   -jobname=eplain -progname=eplain -translate-file=cp227.tcx 
*eplain.ini


Interesting. There are several pdftex here:
[root@salmo /usr/local/texlive/2023/bin/x86_64-linux]# ll pdftex
-rwxr-xr-x 1 root root 2269928 Feb 23  2023 pdftex*
and
/usr/share/texmf-var/fonts/map/
drwxr-xr-x 3 root root 4096 Mar 24  2015 pdftex/
and
/usr/share/texmf-var/web2c/pdftex
drwxr-xr-x 2 root root4096 Jun 20  2020 pdftex/

I think I need to remove /usr/share/texinfo/, /usr/share/texmf-config/,
/usr/share/texmf-dist/, /usr/share/texmf-local/, and /usr/share/texmf-var/.

I thought I had removed all previous TexLive2022 and earlier. Apparently
not.

I'll remove the old directories in /usr/share/ then try tlmgr and pdftex
again.

Regards,

Rich


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: updating TexLive2023: failed

2023-09-24 Thread Herbert Voss



Am 24.09.23 um 21:30 schrieb Rich Shepard:

On Sun, 24 Sep 2023, Herbert Voss wrote:


run it in a terminal:


Herbert,

That's what I did earlier this morning.


tlmgr --self --all update


All up to date; nothing done.


fmtutil-sys --all
Is the error still again there?


Yes, it is:

No pages of output.
Transcript written on dviluatex.log.
fmtutil [INFO]: log file copied to: 
/usr/local/texlive/2023/texmf-var/web2c/luatex/dviluatex.log
fmtutil [INFO]: 
/usr/local/texlive/2023/texmf-var/web2c/luatex/dviluatex.fmt installed.
fmtutil [ERROR]: running `tex -ini   -jobname=lollipop 
-progname=lollipop lollipop.ini 
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `pdftex -ini   -jobname=amstex 
-progname=amstex -translate-file=cp227.tcx *amstex.ini return status: 1


Does this file exists?

/usr/local/texlive/2023/texmf-dist/web2c/cp227.tcx

and try

sudo pdftex -ini   -jobname=eplain -progname=eplain 
-translate-file=cp227.tcx *eplain.ini


should give more error messages



Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: updating TexLive2023: failed

2023-09-24 Thread Rich Shepard

On Sun, 24 Sep 2023, Herbert Voss wrote:


run it in a terminal:


Herbert,

That's what I did earlier this morning.


tlmgr --self --all update


All up to date; nothing done.


fmtutil-sys --all
Is the error still again there?


Yes, it is:

No pages of output.
Transcript written on dviluatex.log.
fmtutil [INFO]: log file copied to: 
/usr/local/texlive/2023/texmf-var/web2c/luatex/dviluatex.log
fmtutil [INFO]: /usr/local/texlive/2023/texmf-var/web2c/luatex/dviluatex.fmt 
installed.
fmtutil [ERROR]: running `tex -ini   -jobname=lollipop -progname=lollipop 
lollipop.ini http://lists.lyx.org/mailman/listinfo/lyx-users


Re: updating TexLive2023: failed

2023-09-24 Thread Herbert Voss



Am 24.09.23 um 15:47 schrieb Rich Shepard:

Last July I set up a weekly cron job to update TexLive2023. It's worked
flawlessly until this morning when the attached mltex.log showed up in my
INBOX.

The mltex.log looks good, but what was not included in the log file 
but was

in the email message root sent me was the following:

fmtutil [INFO]: log file copied to: 
/usr/local/texlive/2023/texmf-var/web2c/pdftex/mltex.log
fmtutil [INFO]: 
/usr/local/texlive/2023/texmf-var/web2c/pdftex/mltex.fmt installed.
fmtutil [ERROR]: running `pdftex -ini   -jobname=amstex 
-progname=amstex -translate-file=cp227.tcx *amstex.ini return status: 1

fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `tex -ini   -jobname=lollipop 
-progname=lollipop lollipop.ini 
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `pdftex -ini   -jobname=eplain 
-progname=eplain -translate-file=cp227.tcx *eplain.ini return status: 1

fmtutil [ERROR]: returning error due to option --strict
fmtutil [INFO]: disabled formats: 3
fmtutil [INFO]: successfully rebuilt formats: 49
fmtutil [INFO]: failed to build: 3 (pdftex/amstex tex/lollipop 
pdftex/eplain)

fmtutil [INFO]: total formats: 55
fmtutil [INFO]: exiting with status 3



run it in a terminal:


tlmgr --self --all update
fmtutil-sys --all


Is the error still again there?

Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Deleting outline entry

2023-09-24 Thread Dan via lyx-users

24 de set. de 2023, 3:25 per xraco...@gmx.de:

> On 2023-09-23 21:09, Daniel wrote:
>
>> On 2023-09-23 18:50, Dan via lyx-users wrote:
>>
 Is there a way to delete an outline entry? A right-click on the entry does
 not offer that option and the delete key removes characters in the
 chapter/section title, not the chapter/section itself.

>>> I do not see any way of accomplishing this via the GUI, but it can be done 
>>> by means of the command interpreter with a pair of commands.
>>>
>>> Say you want to delete section 2.2 of your document
>>>    1. Place the cursor at the title of section 2.2.
>>>    2. Issue in the command interpreter "section-select". This will select 
>>> the whole section 2.2.
>>>    3. To delete the entire section, then enter this command: 
>>> "char-delete-forward". This will erase the whole section.
>>>
>>> These steps work for any kind of sectioning (division of the text 
>>> hierarchycally): parts, chapters, paragraphs, etc. You could even customize 
>>> your UI file to bind these pair of commands to a button in the toolbars.
>>>
>>
>> I was about to suggest to add a "Delete Section" menu entry to the TOC 
>> context menu. But that doesn't work for some reason and I am not sure why.
>>
>> In any case, such a (working) menu entry should probably be available.
>>
>> Daniel
>>
>
> Maybe there is some kind of cursor update missing after the "section-select" 
> command?
>
> command-sequence section-select;char-delete-forward
>
> apparently works fine when the cursor is already in the heading but not when 
> executed merely from the context-menu.
>
> Daniel
>
Apparently the command "char-delete-forward" (and its twin 
"char-delete-backward") is "forbidden" in that location. Thus, adding the item
 "Delete Section|e" "command-sequence section-select; char-delete-forward"
to stdcontext.inc does not work, by design.

Try it by yourself with the debugging category "action" enabled in the messages 
pane (View > Messages Pane). Otherwise, see the debug messages attached.

It may be possible, but I do not know how.


Daniel.
--
Enviat amb Tutanota.
20:12:26.110: Command disabledGuiApplication.cpp (1746): cmd:  action: 173 
[command-sequence]  arg: 'section-select; char-delete-forward' x: 0 y: 0
GuiApplication.cpp (1746): cmd:  action: 332 [section-select]  arg: '' x: 0 y: 0
GuiApplication.cpp (1746): cmd:  action: 196 [paragraph-goto]  arg: '1 0' x: 0 
y: 0
BufferView.cpp (1366): BufferView::dispatch: cmd:  action: 196 [paragraph-goto] 
 arg: '1 0' x: 0 y: 0
GuiApplication.cpp (1514): dispatch msg is `'
Cursor.cpp (781): Cursor::dispatch: cmd:  action: 332 [section-select]  arg: '' 
x: 0 y: 0

Cursor.cpp (811): Cursor::dispatch: cmd:  action: 332 [section-select]  arg: '' 
x: 0 y: 0

insets/InsetText.cpp (311): InsetText::doDispatch(): cmd:  action: 332 
[section-select]  arg: '' x: 0 y: 0
Text.cpp (4038): Text::dispatch: cmd:  action: 332 [section-select]  arg: '' x: 
0 y: 0
GuiApplication.cpp (1514): dispatch msg is `'
GuiApplication.cpp (1746): cmd:  action: 61 [char-delete-forward]  arg: '' x: 0 
y: 0
GuiApplication.cpp (1754): action char-delete-forward [] is disabled at this 
location
GuiApplication.cpp (1514): dispatch msg is `Command disabled'
GuiApplication.cpp (1514): dispatch msg is `'
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


updating TexLive2023: failed

2023-09-24 Thread Rich Shepard

Last July I set up a weekly cron job to update TexLive2023. It's worked
flawlessly until this morning when the attached mltex.log showed up in my
INBOX.

The mltex.log looks good, but what was not included in the log file but was
in the email message root sent me was the following:

fmtutil [INFO]: log file copied to: 
/usr/local/texlive/2023/texmf-var/web2c/pdftex/mltex.log
fmtutil [INFO]: /usr/local/texlive/2023/texmf-var/web2c/pdftex/mltex.fmt 
installed.
fmtutil [ERROR]: running `pdftex -ini   -jobname=amstex -progname=amstex 
-translate-file=cp227.tcx *amstex.ini This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (INITEX)  24 
SEP 2023 05:48
 restricted \write18 enabled.
 %&-line parsing enabled.
 (/usr/local/texlive/2023/texmf-dist/web2c/cp227.tcx)
MLTeX v2.2 enabled
**mltex.ini
(/usr/local/texlive/2023/texmf-dist/tex/mltex/config/mltex.ini
(/usr/local/texlive/2023/texmf-dist/tex/plain/config/tex.ini
(/usr/local/texlive/2023/texmf-dist/tex/plain/base/plain.tex
Preloading the plain format: codes, registers,
\maxdimen=\dimen10
\hideskip=\skip10
\centering=\skip11
\p@=\dimen11
\z@=\dimen12
\z@skip=\skip12
\voidb@x=\box10
 parameters,
\smallskipamount=\skip13
\medskipamount=\skip14
\bigskipamount=\skip15
\normalbaselineskip=\skip16
\normallineskip=\skip17
\normallineskiplimit=\dimen13
\jot=\dimen14
\interdisplaylinepenalty=\count23
\interfootnotelinepenalty=\count24
 fonts, more fonts,
\itfam=\fam4
\slfam=\fam5
\bffam=\fam6
\ttfam=\fam7

macros,
\strutbox=\box11
\mscount=\count25
\tabs=\box12
\tabsyet=\box13
\tabsdone=\box14
 math definitions,
\rootbox=\box15
\p@renwd=\dimen15
 output routines,
\headline=\toks10
\footline=\toks11
\footins=\insert254
\topins=\insert253
 hyphenation
(/usr/local/texlive/2023/texmf-dist/tex/generic/hyphen/hyphen.tex)) ) )
Beginning to dump on file mltex.fmt
 (preloaded format=mltex 2023.9.24)
2785 strings of total length 41707
4998 memory locations dumped; current usage is 116&4879
1087 multiletter control sequences
\font\nullfont=nullfont
\font\tenrm=cmr10
\font\preloaded=cmr9
\font\preloaded=cmr8
\font\sevenrm=cmr7
\font\preloaded=cmr6
\font\fiverm=cmr5
\font\teni=cmmi10
\font\preloaded=cmmi9
\font\preloaded=cmmi8
\font\seveni=cmmi7
\font\preloaded=cmmi6
\font\fivei=cmmi5
\font\tensy=cmsy10
\font\preloaded=cmsy9
\font\preloaded=cmsy8
\font\sevensy=cmsy7
\font\preloaded=cmsy6
\font\fivesy=cmsy5
\font\tenex=cmex10
\font\preloaded=cmss10
\font\preloaded=cmssq8
\font\preloaded=cmssi10
\font\preloaded=cmssqi8
\font\tenbf=cmbx10
\font\preloaded=cmbx9
\font\preloaded=cmbx8
\font\sevenbf=cmbx7
\font\preloaded=cmbx6
\font\fivebf=cmbx5
\font\tentt=cmtt10
\font\preloaded=cmtt9
\font\preloaded=cmtt8
\font\preloaded=cmsltt10
\font\tensl=cmsl10
\font\preloaded=cmsl9
\font\preloaded=cmsl8
\font\tenit=cmti10
\font\preloaded=cmti9
\font\preloaded=cmti8
\font\preloaded=cmti7
\font\preloaded=cmu10
\font\preloaded=cmmib10
\font\preloaded=cmbsy10
\font\preloaded=cmcsc10
\font\preloaded=cmssbx10
\font\preloaded=cmdunh10
\font\preloaded=cmr7 at 14.51799pt
\font\preloaded=cmtt10 at 14.4pt
\font\preloaded=cmssbx10 at 14.4pt
\font\preloaded=manfnt
14787 words of font info for 50 preloaded fonts
14 hyphenation exceptions
Hyphenation trie of length 6075 has 181 ops out of 35111
  181 for language 0
0 words of pdfTeX memory
0 indirect objects
No pages of output.
# actual command line used during this run
# pdftex -ini   -jobname=mltex -progname=mltex -translate-file=cp227.tcx -mltex 
mltex.ini -- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Deleting outline entry

2023-09-23 Thread Rich Shepard

On Sat, 23 Sep 2023, Dan via lyx-users wrote:


I am dumb. I have just realized there is a context-menu item "Select
Section": right-clicking on any section in the outline pane. So you could
just use that and then the "delete" key.


Daniel,

I looked at the choices presented when a right click was made on an item in
the outline pane, but didn't think to use the `Select section' key. Yeah,
that does work to delete the selected section.

Thanks for spending your time on this.

Regards,

Rich

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Deleting outline entry

2023-09-23 Thread Dan via lyx-users


> On 2023-09-23 18:50, Dan via lyx-users wrote:
>
>>> Is there a way to delete an outline entry? A right-click on the entry does
>>> not offer that option and the delete key removes characters in the
>>> chapter/section title, not the chapter/section itself.
>>>
>> I do not see any way of accomplishing this via the GUI, but it can be done 
>> by means of the command interpreter with a pair of commands.
>>
I am dumb. I have just realized there is a context-menu item "Select Section": 
right-clicking on any section in the outline pane. So you could just use that 
and then the "delete" key.


> I was about to suggest to add a "Delete Section" menu entry to the TOC 
> context menu. But that doesn't work for some reason and I am not sure why.
>
> In any case, such a (working) menu entry should probably be available.
>
> Daniel
>
I have just run a couple of tests and, unexpectedly, the sequence of commands 
works when added to the toolbars (only if cursor is in the title), but not when 
added to the context menu of the TOC.
See the attached (diff) files to see the changes I made to "stdcontext.inc" and 
"stdtoolbars.inc", and try it out by yourself.


Daniel.
--
Enviat amb Tutanota.
717d716
< 		Item "Delete Section|S" "command-sequence section-select; char-delete-forward"
106d105
< 		Item "Delete section" "command-sequence section-select; char-delete-forward"
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Deleting outline entry

2023-09-23 Thread Daniel

On 2023-09-23 18:50, Dan via lyx-users wrote:

Is there a way to delete an outline entry? A right-click on the entry does
not offer that option and the delete key removes characters in the
chapter/section title, not the chapter/section itself.


I do not see any way of accomplishing this via the GUI, but it can be done by 
means of the command interpreter with a pair of commands.

Say you want to delete section 2.2 of your document
   1. Place the cursor at the title of section 2.2.
   2. Issue in the command interpreter "section-select". This will select the 
whole section 2.2.
   3. To delete the entire section, then enter this command: 
"char-delete-forward". This will erase the whole section.

These steps work for any kind of sectioning (division of the text 
hierarchycally): parts, chapters, paragraphs, etc. You could even customize 
your UI file to bind these pair of commands to a button in the toolbars.


I was about to suggest to add a "Delete Section" menu entry to the TOC 
context menu. But that doesn't work for some reason and I am not sure why.


In any case, such a (working) menu entry should probably be available.

Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Deleting outline entry

2023-09-23 Thread Rich Shepard

On Sat, 23 Sep 2023, Dan wrote:


I do not see any way of accomplishing this via the GUI, but it can be done
by means of the command interpreter with a pair of commands.

Say you want to delete section 2.2 of your document
  1. Place the cursor at the title of section 2.2.
  2. Issue in the command interpreter "section-select". This will select the 
whole section 2.2.
  3. To delete the entire section, then enter this command: 
"char-delete-forward". This will erase the whole section.

These steps work for any kind of sectioning (division of the text 
hierarchycally): parts, chapters, paragraphs, etc. You could even customize 
your UI file to bind these pair of commands to a button in the toolbars.


Daniel,

Thank you. This makes creating a MWE from a large document much easier.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Deleting outline entry

2023-09-23 Thread Dan via lyx-users


> Is there a way to delete an outline entry? A right-click on the entry does
> not offer that option and the delete key removes characters in the
> chapter/section title, not the chapter/section itself.
>
I do not see any way of accomplishing this via the GUI, but it can be done by 
means of the command interpreter with a pair of commands.

Say you want to delete section 2.2 of your document
  1. Place the cursor at the title of section 2.2.
  2. Issue in the command interpreter "section-select". This will select the 
whole section 2.2.
  3. To delete the entire section, then enter this command: 
"char-delete-forward". This will erase the whole section.

These steps work for any kind of sectioning (division of the text 
hierarchycally): parts, chapters, paragraphs, etc. You could even customize 
your UI file to bind these pair of commands to a button in the toolbars.

If you do not know how to open the command interpreter, do this
  1. Place the mouse pointer on the toolbars.
  2. Right click and set the toolbar "Command Buffer" visibility to "On".

This will bring up a text box to type command in. Use the tab key when typing 
to autocomplete commands.

Hope this helps. Kind regards.


Daniel.
--
Enviat amb Tutanota.
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Problem converting some svgz

2023-09-22 Thread Dan via lyx-users


> On Fri, Sep 15, 2023 at 07:25:44PM +0200, Dan via lyx-users wrote:
>
>> Yes, I did, that's why I suspect the problem is actually with these 
>> third-party apps rather than LyX.
>> Generate PDF files (attached) from redo.svgz
>>  1. Cairosvg: "cairosvg -f pdf -o redo_cairosvg.pdf lib/images/redo.svgz"
>>  2. Inkscape: "inkscape -D -o redo_inkscape.pdf lib/images/redo.svgz"
>>
>
> I could reproduce the problem with Inkscape. I can actually open the file in 
> Inkscape and it looks fine (though there are Warning on the console about svg 
> content).
> It's the export when it breaks completely. I suggest to file bug against 
> inkscape itself.
>
Asked for peer confirmation on IRC as well. A person replied to me confirming 
the problem with version 1.3; but also told me that this problem does not 
happen in the upstream version (1.4-dev) of Inkscape.

That person recommended me to file a bug so that the "fix" is backported to the 
next release of Inkscape (1.3.1).


> For LyX purposes you could bypass this problem by using rsvg-convert instead 
> of inkscape (works fine here).
> Another way could by to try luck in different vector editor, resave it and 
> try again.
>
> Pavel
>
Thanks for the suggestion! I stopped using Inkscape because the packaged 
AppImage is quite slow compared to other options, such as cairosvg. Will give 
it a try.


Daniel.
--
Enviat amb Tutanota.
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Need help finding error

2023-09-22 Thread Rich Shepard

On Fri, 22 Sep 2023, Herbert Voss wrote:


Instead of \S try to insert directly (not in ERT) the § symbol


Herbert,

I haven't had issues using \S when dealing with federal law and state
statute sections. And I don't know how to enter the symbol in LyX without
using ERT.

Many thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Need help finding error

2023-09-22 Thread Rich Shepard

On Fri, 22 Sep 2023, Herbert Voss wrote:


that is the deafult behaviour if you have a problem in a LaTeX run and the
created helper files for biber are corrupt. Simply ignore it, and run the
_document_ again. If it doesn't help then delete the file mwe.bcf, which
is a BiberConfigFile.


Herbert,

I've re-compiled failed builds before and didn't think of doing so this
time. Normally, I'd prefer to fix the problem, but in this case as long as I
have the PDF to deliver to my client, all's good.

Many thanks for the reminder.

Best regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Need help finding error

2023-09-22 Thread Herbert Voss



Am 21.09.23 um 19:01 schrieb Rich Shepard:
I've not successfully built a MWE; each time I remove text either 
above or

below the highlighted error the document compiles successfully. The
unmodified doc doesn't.

Attached is an image of the highlighted line and following text along 
with
the error reporting box, and the complete error log file. I do not see 
the

error there.

I need help identifying the source of this error. FWIW, the doc built
successfully before I added more text below where the error is shown.


Instead of \S try to insert directly (not in ERT) the § symbol

Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Need help finding error

2023-09-22 Thread Herbert Voss




Am 21.09.23 um 23:02 schrieb Rich Shepard:


On Thu, 21 Sep 2023, Rich Shepard wrote:


I need help identifying the source of this error. FWIW, the doc built
successfully before I added more text below where the error is shown.


I've learned that the error is in biber's processing of the bibliography.
The biber error log is in the attached image and I have no idea how to 
use

it to find why mwe.bcf is malformed.



Rich,
that is the deafult behaviour if you have a problem in a LaTeX run
and the created helper files for biber are corrupt. Simply ignore it,
and run the _document_ again. If it doesn't help then delete the
file mwe.bcf, which is a BiberConfigFile.

Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Need help finding error

2023-09-21 Thread Rich Shepard


On Thu, 21 Sep 2023, Rich Shepard wrote:


I need help identifying the source of this error. FWIW, the doc built
successfully before I added more text below where the error is shown.


I've learned that the error is in biber's processing of the bibliography.
The biber error log is in the attached image and I have no idea how to use
it to find why mwe.bcf is malformed.

Help, please,

Rich-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Need help finding error

2023-09-21 Thread Rich Shepard

I've not successfully built a MWE; each time I remove text either above or
below the highlighted error the document compiles successfully. The
unmodified doc doesn't.

Attached is an image of the highlighted line and following text along with
the error reporting box, and the complete error log file. I do not see the
error there.

I need help identifying the source of this error. FWIW, the doc built
successfully before I added more text below where the error is shown.

TIA,

RichThis is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded 
format=pdflatex 2023.9.17)  21 SEP 2023 09:48
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**mwe.tex
(./mwe.tex
LaTeX2e <2023-06-01> patch level 1
L3 programming layer <2023-08-29>

(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2023/07/07 v3.41 KOMA-Script document class (report)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2023/07/07 v3.41 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2023/07/07 v3.41 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2023/07/07 v3.41 KOMA-Script package (file load hooks)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
Package: scrlfile-hook 2023/07/07 v3.41 KOMA-Script package (using LaTeX hooks)

(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrlogo.sty
Package: scrlogo 2023/07/07 v3.41 KOMA-Script package (logo)
))) (/usr/local/texlive/2023/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2022/05/29 v1.15 key=value parser (DPC)
\KV@toks@=\toks17
)
Applying: [2021/05/01] Usage of raw or classic option list on input line 252.
Already applied: [/00/00] Usage of raw or classic option list on input line
 368.
)) (/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2023/07/07 v3.41 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip48
\scr@dte@tocline@numbox=\box51
)
Package tocbasic Info: omitting babel extension for `toc'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `toc' on input line 135.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt)   file `scrsize11.clo' to setup font sizes on input line 268
8.
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File: scrsize11pt.clo 2023/07/07 v3.41 KOMA-Script font size class option (11pt
)
) (/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2023/07/07 v3.41 KOMA-Script package (type area)
\ta@bcor=\skip49
\ta@div=\count185
\ta@hblk=\skip50
\ta@vblk=\skip51
\ta@temp=\skip52
\footheight=\skip53
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 418.2pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 47.2316pt
(typearea)  \oddsidemargin  = -12.5192pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 514.20023pt
(typearea)  \topmargin  = 12.2347pt
(typearea)  \headheight = 17.0pt
(typearea)  \headsep= 20.40001pt
(typearea)  \topskip= 11.0pt
(typearea)  \footskip   = 47.6pt
(typearea)  \baselineskip   = 13.6pt
(typearea)  on input line 1799.
)
\c@part=\count186
\c@chapter=\count187
\c@section=\count188
\c@subsection=\count189
\c@subsubsection=\count190
\c@paragraph=\count191
\c@subparagraph=\count192
\scr@dte@chapter@maxnumwidth=\skip54
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\chapter on input line 5994.
\scr@dte@section@maxnumwidth=\skip55
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\section on input line 6005.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\section on input line 6005.
\scr@dte@part@maxnumwidth=\skip56
Class scrreprt Info: using compatibility default `afterindent=true'
(scrreprt)   for `\part on input line 6014.
\scr@dte@subsection@maxnumwidth=\skip57
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsection on input line 6024.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsection on input line 6024.
\scr@dte@subsubsection@maxnumwidth=\skip58
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsubsection 

Deleting outline entry

2023-09-21 Thread Rich Shepard

A document that had built before now fails with an error. I'm trying to
isolate the error and want to delete chapters one-by-one before and after
the highlighted error.

Is there a way to delete an outline entry? A right-click on the entry does
not offer that option and the delete key removes characters in the
chapter/section title, not the chapter/section itself.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Problem with frame inset

2023-09-20 Thread jspitzm
Am Dienstag, dem 19.09.2023 um 15:43 +0200 schrieb Dan:
> I have come across the very same problem again with listing buttons
> (when editing externally). The solution is the very same as well.
> 
> STEPS TO REPRODUCE:
>    1. Insert > Program listing
>    2. Type something in.
>    3. Open context menu (right clic) and choose "Edit externally".
>    4. A button for the program listing inset shows whose text is
> barely readable. See attached image.
> 
> SOLUTION:
> I have tried mimicking your solution to the previous problem:
> switching the label's text colour from "foreground" to "black". See
> the text attachment (diff of changes to lib/layouts/stdinsets.inc)

Yes, perfect. I've done the change. I also verified that there is no
more missed case in stdinsets (there's another foreground case in
IPADeco, but this one's correct).

Best,
Jürgen

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


<    3   4   5   6   7   8   9   10   11   12   >