Re: Beta 4 Tarballs

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 18:23 -0400 schrieb Richard Kimberly Heck: > On 8/29/23 04:46, Jürgen Spitzmüller wrote: > > Am Dienstag, dem 29.08.2023 um 07:18 +0200 schrieb Stephan Witt: > > > The included graphics have absolute paths. AFAICS it’s only in > > > Intro.lyx. > > I fixed that in mast

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 23:30 +0200 schrieb Pavel Sanda: > Quick check shows that the new approach breaks in multiple ways on my > system. I'd like to see those. > I'm sure there are ways to gradually fix this but I have different > proposal. > > Would you mind that instead of just checki

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 17:50 +0200 schrieb Pavel Sanda: > - Not waiting for a viewer to finish & spawn multiples instances of > viewer Don't see this problem, but if it is there, we can go async. >   when more result on one query is found > - eat STDERR output to avoid mysterious crashes

Preview error on removing last row of table

2023-08-29 Thread Andrew Parsloe
Version 2.4.0-beta3-devel (Sunday, 11 December 2022) Qt Version (run-time): 6.5.1 on platform windows Put a small table inside a preview inset, move the cursor outside the inset and wait for the preview to form. Now delete the last row of the table by clicking the icon or Alt+M W D and move the

Re: Beta 4 Tarballs

2023-08-29 Thread Richard Kimberly Heck
On 8/29/23 04:46, Jürgen Spitzmüller wrote: Am Dienstag, dem 29.08.2023 um 07:18 +0200 schrieb Stephan Witt: The included graphics have absolute paths. AFAICS it’s only in Intro.lyx. I fixed that in master. Is this bad enough to rebuild? Riki -- lyx-devel mailing list lyx-devel@lists.lyx.o

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Tue, Aug 29, 2023 at 05:50:12PM +0200, Pavel Sanda wrote: > On Tue, Aug 29, 2023 at 05:27:16PM +0200, Jürgen Spitzmüller wrote: > > Am Dienstag, dem 29.08.2023 um 17:23 +0200 schrieb Pavel Sanda: > > > I am afraid this will break on the problems I tried to handle inside > > > the script and will

Re: [LyX/master] Fixup 7f1b1729: restore lazy caret handling

2023-08-29 Thread Scott Kostyshak
On Mon, Jun 26, 2023 at 03:44:51AM -0400, Scott Kostyshak wrote: > On Mon, Jun 26, 2023 at 09:20:17AM +0200, Jean-Marc Lasgouttes wrote: > > Le 25/06/2023 à 13:05, Scott Kostyshak a écrit : > > > My main motivation is to annoy JMarc with issues that no one else notices > > > :) > > > > And you ar

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Tue, Aug 29, 2023 at 05:27:16PM +0200, Jürgen Spitzmüller wrote: > Am Dienstag, dem 29.08.2023 um 17:23 +0200 schrieb Pavel Sanda: > > I am afraid this will break on the problems I tried to handle inside > > the script and will complicate the situation if you want to slip your > > own scripts in

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 17:23 +0200 schrieb Pavel Sanda: > I am afraid this will break on the problems I tried to handle inside > the script and will complicate the situation if you want to slip your > own scripts in the pipeline. Like which problems exactly? > If you have strong feeling t

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Tue, Aug 29, 2023 at 04:57:01PM +0200, Jürgen Spitzmüller wrote: > Am Dienstag, dem 29.08.2023 um 14:52 +0200 schrieb Jürgen Spitzmüller: > > OTOH if we would make the lyxpaperview script return a path rather > > than opening found documents itself, we could use the same message > > and be more

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 16:57 +0200 schrieb Jürgen Spitzmüller: > Am Dienstag, dem 29.08.2023 um 14:52 +0200 schrieb Jürgen > Spitzmüller: > > OTOH if we would make the lyxpaperview script return a path rather > > than opening found documents itself, we could use the same message > > and be

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 14:52 +0200 schrieb Jürgen Spitzmüller: > OTOH if we would make the lyxpaperview script return a path rather > than opening found documents itself, we could use the same message > and be more precise here. Like in the attached. -- Jürgen diff --git a/lib/scripts/ly

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Tue, Aug 29, 2023 at 03:13:47PM +0200, Pavel Sanda wrote: > See the attached for the hint and below: now with the patch... p diff --git a/src/frontends/qt/ui/PrefEditUi.ui b/src/frontends/qt/ui/PrefEditUi.ui index 79820b7c7d..39b05dcbc5 100644 --- a/src/frontends/qt/ui/PrefEditUi.ui +++ b/src/f

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Tue, Aug 29, 2023 at 01:16:40PM +0200, Pavel Sanda wrote: > 3 is disabled by default and hint can be added later as well. See the attached for the hint and below: (ATM I'm not on the machine with commit access, so please add yourself if you are pushing new release out.) For the section 6.6.4

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 14:44 +0200 schrieb Jürgen Spitzmüller: > I had to introduce a specific message for the EXTERNAL case, as we do > not have an URI at hand in this case. OTOH if we would make the lyxpaperview script return a path rather than opening found documents itself, we could us

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Tue, Aug 29, 2023 at 02:16:01PM +0200, Daniel wrote: > Or would that be too annoying? Quite a lot. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 13:22 +0200 schrieb Pavel Sanda: > That would be much appreciated. > > Please go on if you have time, I sent my edits in the thread itself. Committed. Please check. I had to introduce a specific message for the EXTERNAL case, as we do not have an URI at hand in thi

Re: Next Release?

2023-08-29 Thread Scott Kostyshak
On Tue, Aug 29, 2023 at 02:16:01PM +0200, Daniel wrote: > On 2023-08-29 13:16, Pavel Sanda wrote: > > On Mon, Aug 28, 2023 at 08:49:30PM -0400, Richard Kimberly Heck wrote: > > > > Options are, we postpone this for 2.4.1 as this is not fileformat > > > > change. > > > > If deemed too dangerous, we

Re: Next Release?

2023-08-29 Thread Daniel
On 2023-08-29 13:16, Pavel Sanda wrote: On Mon, Aug 28, 2023 at 08:49:30PM -0400, Richard Kimberly Heck wrote: Options are, we postpone this for 2.4.1 as this is not fileformat change. If deemed too dangerous, we can temporarily disable the feature and enable it again with the safeguards, your c

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Tue, Aug 29, 2023 at 10:39:55AM +0200, Jürgen Spitzmüller wrote: > Am Montag, dem 28.08.2023 um 21:26 +0200 schrieb Pavel Sanda: > > I do not have currently capacity to work on the citation/url links opening > > policy. As it seems there is some vague consensus on how to proceed and > > that wil

Re: Policy for opening url links in documents

2023-08-29 Thread Pavel Sanda
On Thu, Aug 17, 2023 at 08:54:43AM +0200, Jürgen Spitzmüller wrote: > So a dialog that says: > > > LyX wants to open the following link in an external application: > > Be aware that this might entail security infringements. Only do this if > you trust origin of the document and the target of

Re: Next Release?

2023-08-29 Thread Pavel Sanda
On Mon, Aug 28, 2023 at 08:49:30PM -0400, Richard Kimberly Heck wrote: > >Options are, we postpone this for 2.4.1 as this is not fileformat change. > >If deemed too dangerous, we can temporarily disable the feature and enable > >it again with the safeguards, your call here. > > Can you remind me w

Re: Beta 4 Tarballs

2023-08-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.08.2023 um 07:18 +0200 schrieb Stephan Witt: > The included graphics have absolute paths. AFAICS it’s only in > Intro.lyx. I fixed that in master. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Next Release?

2023-08-29 Thread Jürgen Spitzmüller
Am Montag, dem 28.08.2023 um 21:26 +0200 schrieb Pavel Sanda: > I do not have currently capacity to work on the citation/url links > opening > policy. As it seems there is some vague consensus on how to proceed > and > that will involve new string(s). > > Options are, we postpone this for 2.4.1 a