Undo does not work after external change

[Scott Kostyshak]

The following is the same on 2.3.0 and master:

1. Open a .lyx file in LyX
2. Make a change to the .lyx file externally (e.g., open in a text
   editor and change something).
3. Reload the file in LyX
4. Undo

Undo is disabled. Should it revert to the state before reloading? Not
sure it is close enough, but in Vim, if I reload a file (with ":e"), I
can undo that reload.

Scott


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

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2273

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2273/--
Started by an SCM change
Building remotely on lyx-linux1 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
java.io.IOException: Failed to mkdirs: 

at hudson.FilePath.mkdirs(FilePath.java:1191)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1267)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Jenkins build is back to normal : Build branch "master" » ubuntu-latest-qt5-cmake #2369

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-latest-qt5-cmake/2369/
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: An official GitHub mirror for LyX?

[Thibaut Cuvelier]

On Mon, 7 Dec 2020 at 19:24, Jean-Marc Lasgouttes 
wrote:

> Le 07/12/2020 à 00:17, Yuriy Skalko a écrit :
> > What about replacing Trac with Gitea? I have very successful experience
> > with it -- simple to install, very fast and lightweight.
>
> It looks nice indeed, although I mostly saw the interface :)
>
> One other issue I see with it is that it means we still administrate our
> server wrt git and tickets. We do not have a server maintainer (unless I
> am dismissing someone? I am not one myself) currently and it kind of
> "just works". At least having a gitlab solution would allow us to choose
> where it is hosted (osuosl has one, actually).
>
> The good point about a self-hosted gitea is that it would be lightweight.
>
> Then we have to see how much of our trac data will be lost in translation.
>

Keeping the data would be a pain point… (By the way, I never suggested
moving away from trac in the first place :P.)

On GitLab.com, you can import "an exported GitLab project", or from
software forges like GitHub or Gitea. https://github.com/tracboat/tracboat
could be a solution to make that GitLab export in the first place. It looks
reasonably easy to use.
In this kind of workflow, I think it would be best to avoid Gitea, to avoid
losing even more data.

By the way, what about Jenkins/CI? GitLab proposes a free service for this,
but only 400 minutes per month (https://about.gitlab.com/pricing/). You can
have more by contacting them:
https://about.gitlab.com/solutions/open-source/join/.

Such a migration would require a lot of discussion, notably about the way
of collaborating to LyX: it would allow doing push requests instead of
sending patches to the mailing list, for instance. I think Guillaume is
already for this change (https://gitlab.com/gadmm).
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: An official GitHub mirror for LyX?

[Jean-Marc Lasgouttes]

Le 07/12/2020 à 00:17, Yuriy Skalko a écrit :
What about replacing Trac with Gitea? I have very successful experience 
with it -- simple to install, very fast and lightweight.


It looks nice indeed, although I mostly saw the interface :)

One other issue I see with it is that it means we still administrate our 
server wrt git and tickets. We do not have a server maintainer (unless I 
am dismissing someone? I am not one myself) currently and it kind of 
"just works". At least having a gitlab solution would allow us to choose 
where it is hosted (osuosl has one, actually).


The good point about a self-hosted gitea is that it would be lightweight.

Then we have to see how much of our trac data will be lost in translation.

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

Re: Disable stuff automatically in dialogs with read-only

[Jean-Marc Lasgouttes]

Le 02/12/2020 à 15:35, Jürgen Spitzmüller a écrit :

Am Dienstag, dem 01.12.2020 um 10:46 -0500 schrieb Richard Kimberly
Heck:

Jürgen knows the most about this, I think, but my sense is that (2)
is
the way to go. I find the ButtonController quite difficult to use.


I tend to agree.


OK, I have handled the search-type and spell-type dialogs.

Now what do we expect for other document-related dialog. The three 
solutions are


1/ disable the dialog (like GuiCharacter)
2/ disable each and every widget when the document is read-only 
(GuiExternal, but the ButtonController::addReadOnly thing is broken as 
you know))

3/ or just rely on the button controller to disable the OK/Apply buttons?

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

Re: Problem with session handling on Linux

[Paul A. Rubin]

On 12/7/20 6:20 AM, José Abílio Matos wrote:


On Monday, December 7, 2020 10:04:03 AM WET Pavel Sanda wrote:

> Can you reproduce your problem with kill -9 $LYXPID ?

>

> Pavel


Yes.


In order to define a minimal example do the following.


1) Open LyX with the last opened files.

2) Create a new file and save it (this is important).

3) Kill the lyx instance with signal -9.

4) Reopen lyx and no file will be open we see only the spash screen.


Can you reproduce this?


Best regards,

--

José Abílio




I can reproduce it (Linux Mint 20, LyX 2.3.5.2). I used "pkill lyx" 
rather than "kill -9 ...", which probably makes no difference.


Paul

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

Re: Unicode characters showing encircled alphanumerics

[Pavel Sanda]

On Mon, Dec 07, 2020 at 04:55:42PM +0100, Guenter Milde wrote:
> > I just used these the other day, via mathed. So I would think they are
> > useful at least sometimes...
> 
> While useful sometimes, we should check whether this does more harm than
> good, especially with fonts other than CM or LM.

Would you mind checking that? I am in no way pushing this patch and if
you think it's not good idea we leave it as it is...

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

Re: Unicode characters showing encircled alphanumerics

[Guenter Milde]

On  7.12.20, Richard Kimberly Heck wrote:
> On 12/7/20 10:29 AM, Pavel Sanda wrote:
> > Hi,
> >
> > this is presumably for Guenter.
> >
> > I found somewhat outdated patch which unfortuntaely never made it to this 
> > list
> > on time. Its for unicodesymbols allowing unicode characters showing 
> > encircled
> > alphanumerics, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724820 
> > .
> > The diff against old 2.0.x is attached, to update it against the current
> > version might not be that hard.
> >
> > Is this worth adding to our codebase?

> I just used these the other day, via mathed. So I would think they are
> useful at least sometimes...

While useful sometimes, we should check whether this does more harm than
good, especially with fonts other than CM or LM.

Günter

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

Re: Unicode characters showing encircled alphanumerics

[Pavel Sanda]

On Mon, Dec 07, 2020 at 10:47:13AM -0500, Richard Kimberly Heck wrote:
> > I found somewhat outdated patch which unfortuntaely never made it to this 
> > list
> > on time. Its for unicodesymbols allowing unicode characters showing 
> > encircled
> > alphanumerics, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724820 
> > .
> > The diff against old 2.0.x is attached, to update it against the current
> > version might not be that hard.
> >
> > Is this worth adding to our codebase?
> 
> I just used these the other day, via mathed. So I would think they are
> useful at least sometimes...

This probably means that one column in unicodesymbols should contain some math
equivalent for each character? In any case I am not sure what should be in the
flags and preamble columns, this patch is from times we did not have those.

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

Re: Unicode characters showing encircled alphanumerics

[Richard Kimberly Heck]

On 12/7/20 10:29 AM, Pavel Sanda wrote:
> Hi,
>
> this is presumably for Guenter.
>
> I found somewhat outdated patch which unfortuntaely never made it to this list
> on time. Its for unicodesymbols allowing unicode characters showing encircled
> alphanumerics, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724820 .
> The diff against old 2.0.x is attached, to update it against the current
> version might not be that hard.
>
> Is this worth adding to our codebase?

I just used these the other day, via mathed. So I would think they are
useful at least sometimes...

Riki


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

Unicode characters showing encircled alphanumerics

[Pavel Sanda]

Hi,

this is presumably for Guenter.

I found somewhat outdated patch which unfortuntaely never made it to this list
on time. Its for unicodesymbols allowing unicode characters showing encircled
alphanumerics, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724820 .
The diff against old 2.0.x is attached, to update it against the current
version might not be that hard.

Is this worth adding to our codebase?

Pavel
--- lib/unicodesymbols	2020-12-07 16:17:48.727230983 +0100
+++ /tmp/unicode	2020-12-07 16:18:25.719412815 +0100
@@ -1845,6 +1845,85 @@
 #
 0x2422 "\\textblank"  "textcomp" "" # BLANK SYMBOL
 0x2423 "\\textvisiblespace"   "textcomp" "" # OPEN BOX
+
+#
+# circled letters
+#
+#0x24c7 "\\textcircled{\small{R}}}"   "textcomp" "" # CIRCLED CAPITAL R
+0x24ea "\\textcircled{\footnotesize{0}}"   "textcomp" "" # CIRCLED DIGIT 0
+0x2460 "\\textcircled{\footnotesize{1}}"   "textcomp" "" # CIRCLED DIGIT 1
+0x2461 "\\textcircled{\footnotesize{2}}"   "textcomp" "" # CIRCLED DIGIT 2
+0x2462 "\\textcircled{\footnotesize{3}}"   "textcomp" "" # CIRCLED DIGIT 3
+0x2463 "\\textcircled{\footnotesize{4}}"   "textcomp" "" # CIRCLED DIGIT 4
+0x2464 "\\textcircled{\footnotesize{5}}"   "textcomp" "" # CIRCLED DIGIT 5
+0x2465 "\\textcircled{\footnotesize{6}}"   "textcomp" "" # CIRCLED DIGIT 6
+0x2466 "\\textcircled{\footnotesize{7}}"   "textcomp" "" # CIRCLED DIGIT 7
+0x2467 "\\textcircled{\footnotesize{8}}"   "textcomp" "" # CIRCLED DIGIT 8
+0x2468 "\\textcircled{\footnotesize{9}}"   "textcomp" "" # CIRCLED DIGIT 9
+0x2469 "\\textcircled{\footnotesize{10}}"   "textcomp" "" # CIRCLED NUMBER 10
+0x246a "\\textcircled{\footnotesize{11}}"   "textcomp" "" # CIRCLED NUMBER 11
+0x246b "\\textcircled{\footnotesize{12}}"   "textcomp" "" # CIRCLED NUMBER 12
+0x246c "\\textcircled{\footnotesize{13}}"   "textcomp" "" # CIRCLED NUMBER 13
+0x246d "\\textcircled{\footnotesize{14}}"   "textcomp" "" # CIRCLED NUMBER 14
+0x246e "\\textcircled{\footnotesize{15}}"   "textcomp" "" # CIRCLED NUMBER 15
+0x246f "\\textcircled{\footnotesize{16}}"   "textcomp" "" # CIRCLED NUMBER 16
+0x2470 "\\textcircled{\footnotesize{17}}"   "textcomp" "" # CIRCLED NUMBER 17
+0x2471 "\\textcircled{\footnotesize{18}}"   "textcomp" "" # CIRCLED NUMBER 18
+0x2472 "\\textcircled{\footnotesize{19}}"   "textcomp" "" # CIRCLED NUMBER 19
+0x2473 "\\textcircled{\footnotesize{20}}"   "textcomp" "" # CIRCLED NUMBER 20
+0x24b6 "\\textcircled{\footnotesize{A}}"   "textcomp" "" # CIRCLED CAPITAL A
+0x24b7 "\\textcircled{\footnotesize{B}}"   "textcomp" "" # CIRCLED CAPITAL B
+0x24b8 "\\textcircled{\footnotesize{C}}"   "textcomp" "" # CIRCLED CAPITAL C
+0x24b9 "\\textcircled{\footnotesize{D}}"   "textcomp" "" # CIRCLED CAPITAL D
+0x24ba "\\textcircled{\footnotesize{E}}"   "textcomp" "" # CIRCLED CAPITAL E
+0x24bb "\\textcircled{\footnotesize{F}}"   "textcomp" "" # CIRCLED CAPITAL F
+0x24bc "\\textcircled{\footnotesize{G}}"   "textcomp" "" # CIRCLED CAPITAL G
+0x24bd "\\textcircled{\footnotesize{H}}"   "textcomp" "" # CIRCLED CAPITAL H
+0x24be "\\textcircled{\footnotesize{I}}"   "textcomp" "" # CIRCLED CAPITAL I
+0x24bf "\\textcircled{\footnotesize{J}}"   "textcomp" "" # CIRCLED CAPITAL J
+0x24c0 "\\textcircled{\footnotesize{K}}"   "textcomp" "" # CIRCLED CAPITAL K
+0x24c1 "\\textcircled{\footnotesize{L}}"   "textcomp" "" # CIRCLED CAPITAL L
+0x24c2 "\\textcircled{\footnotesize{M}}"   "textcomp" "" # CIRCLED CAPITAL M
+0x24c3 "\\textcircled{\footnotesize{N}}"   "textcomp" "" # CIRCLED CAPITAL N
+0x24c4 "\\textcircled{\footnotesize{O}}"   "textcomp" "" # CIRCLED CAPITAL O
+0x24c5 "\\textcircled{\footnotesize{P}}"   "textcomp" "" # CIRCLED CAPITAL P
+0x24c6 "\\textcircled{\footnotesize{Q}}"   "textcomp" "" # CIRCLED CAPITAL Q
+0x24c7 "\\textcircled{\footnotesize{R}}"   "textcomp" "" # CIRCLED CAPITAL R
+0x24c8 "\\textcircled{\footnotesize{S}}"   "textcomp" "" # CIRCLED CAPITAL S
+0x24c9 "\\textcircled{\footnotesize{T}}"   "textcomp" "" # CIRCLED CAPITAL T
+0x24ca "\\textcircled{\footnotesize{U}}"   "textcomp" "" # CIRCLED CAPITAL U
+0x24cb "\\textcircled{\footnotesize{V}}"   "textcomp" "" # CIRCLED CAPITAL V
+0x24cc "\\textcircled{\footnotesize{W}}"   "textcomp" "" # CIRCLED CAPITAL W
+0x24cd "\\textcircled{\footnotesize{X}}"   "textcomp" "" # CIRCLED CAPITAL X
+0x24ce "\\textcircled{\footnotesize{Y}}"   "textcomp" "" # CIRCLED CAPITAL Y
+0x24cf "\\textcircled{\footnotesize{Z}}"   "textcomp" "" # CIRCLED CAPITAL Z
+0x24d0 "\\textcircled{\footnotesize{a}}"   "textcomp" "" # CIRCLED SMALL a
+0x24d1 "\\textcircled{\footnotesize{b}}"   "textcomp" "" # CIRCLED SMALL b

Spellcheck suggestions not visible in context meny of Frame environment

[Pavel Sanda]

Hi,

as stated in title, the spellcheck suggestions are not added to the context menu
for the misspelled word as is the case in usual text. You have to be in the 
'Frame title' inset you usually see in Frame environment.

Its both branch and master.

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

Re: Problem with session handling on Linux

[José Abílio Matos]

On Monday, December 7, 2020 10:04:03 AM WET Pavel Sanda wrote:
> Can you reproduce your problem with kill -9 $LYXPID ?
> 
> Pavel

Yes.

In order to define a minimal example do the following.

1) Open LyX with the last opened files.
2) Create a new file and save it (this is important).
3) Kill the lyx instance with signal -9.
4) Reopen lyx and no file will be open we see only the spash screen.

Can you reproduce this?

Best regards,
-- 
José Abílio-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Problem with session handling on Linux

[Pavel Sanda]

On Mon, Dec 07, 2020 at 09:15:51AM +, José Abílio Matos wrote:
> I happened to me before in another laptop that had a thermal shutdown, there 
> it happened the same thing. So I guess that this falls in the "something more 
> brutal" category. :-D

Can you reproduce your problem with kill -9 $LYXPID ?

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

Re: Problem with session handling on Linux

[José Abílio Matos]

On Sunday, December 6, 2020 10:01:42 PM WET Jean-Marc Lasgouttes wrote:
> OK, what would be a forced shutdow? Run lyx from console and kill it
> with Ctrl+C, or something more brutal?
> 
> JMarc

Basically the whole graphical session crashed. I was in a zoom session and 
there was some button that was not showing up and so I clicked in a quick 
succession on maximize/minimize and at some point X crashed.

I happened to me before in another laptop that had a thermal shutdown, there 
it happened the same thing. So I guess that this falls in the "something more 
brutal" category. :-D

Thank you,
-- 
José Abílio-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel