Re: File format increases on master make it hard to test

2024-04-08 Thread Scott Kostyshak
On Mon, Apr 08, 2024 at 10:14:07AM GMT, José Matos wrote:
> On Sun, 2024-04-07 at 23:03 -0400, Scott Kostyshak wrote:
> > Thanks, that is a good idea, but I would not want to use that setting
> > for most of my documents. I find that doing repeated lyx2lyx does not
> > create a smooth workflow.
> > 
> > Scott
> 
> I pushed against the guarantee before. :-)
> The rationale was the main priority was to ensure the best upgrade
> (forward).
> 
> On the other hand after hundreds of file updates we have now a better
> understanding of what it involves and so I think that with some small
> effort we can improve, make it for a smoother experience, the round
> trip experience.
> 
> BTW, I know that this is orthogonal to your issue. :-)

Fair enough! You are more optimistic than I about making roundtrip smooth :)

Scott


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


Re: File format increases on master make it hard to test

2024-04-08 Thread José Matos
On Sun, 2024-04-07 at 23:03 -0400, Scott Kostyshak wrote:
> Thanks, that is a good idea, but I would not want to use that setting
> for most of my documents. I find that doing repeated lyx2lyx does not
> create a smooth workflow.
> 
> Scott

I pushed against the guarantee before. :-)
The rationale was the main priority was to ensure the best upgrade
(forward).

On the other hand after hundreds of file updates we have now a better
understanding of what it involves and so I think that with some small
effort we can improve, make it for a smoother experience, the round
trip experience.

BTW, I know that this is orthogonal to your issue. :-)
-- 
José Abílio
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: File format increases on master make it hard to test

2024-04-07 Thread Scott Kostyshak
On Sun, Apr 07, 2024 at 03:13:44PM GMT, Richard Kimberly Heck wrote:
> On 4/7/24 12:46, José Matos wrote:
> > On Sun, 2024-04-07 at 11:31 -0400, Scott Kostyshak wrote:
> > > Fair enough. That was what I was afraid of (and expected).
> > > 
> > > Scott
> > A possible mid-term solution, to your use case, is to set the output
> > format of the latest stable version.
> > 
> > This would mean that any document is always imported to the latest
> > development release and when saved it is done in the stable file
> > format.
> > 
> > On the other hand what this would mean to stress the
> > conversion/reversion round trip.
> > 
> > This could be implemented as some kind of option to set, by default,
> > the save file format version or even better, because in this case this
> > is what it intended, the target version.
> > 
> > In the preferences file this could go as:
> > 
> > \save_file_format 2.4
> > 
> > If this option is not set then everything works as usual.
> > If it is set then, when the file is saved, the file is reverted to that
> > file format.
> > 
> > I hope that this idea helps, :-)
> 
> That is a good idea. It's too late for 2.4.x, but if it were added early to
> master, then it would be usable for Scott's purpose.
> 
> The roundtrip would of course only matter if one made use of features that
> required a format change.

Thanks, that is a good idea, but I would not want to use that setting
for most of my documents. I find that doing repeated lyx2lyx does not
create a smooth workflow.

Scott


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


Re: File format increases on master make it hard to test

2024-04-07 Thread Richard Kimberly Heck

On 4/7/24 12:46, José Matos wrote:

On Sun, 2024-04-07 at 11:31 -0400, Scott Kostyshak wrote:

Fair enough. That was what I was afraid of (and expected).

Scott

A possible mid-term solution, to your use case, is to set the output
format of the latest stable version.

This would mean that any document is always imported to the latest
development release and when saved it is done in the stable file
format.

On the other hand what this would mean to stress the
conversion/reversion round trip.

This could be implemented as some kind of option to set, by default,
the save file format version or even better, because in this case this
is what it intended, the target version.

In the preferences file this could go as:

\save_file_format 2.4

If this option is not set then everything works as usual.
If it is set then, when the file is saved, the file is reverted to that
file format.

I hope that this idea helps, :-)


That is a good idea. It's too late for 2.4.x, but if it were added early 
to master, then it would be usable for Scott's purpose.


The roundtrip would of course only matter if one made use of features 
that required a format change.


Riki


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


Re: File format increases on master make it hard to test

2024-04-07 Thread José Matos
On Sun, 2024-04-07 at 11:31 -0400, Scott Kostyshak wrote:
> Fair enough. That was what I was afraid of (and expected).
> 
> Scott

A possible mid-term solution, to your use case, is to set the output
format of the latest stable version.

This would mean that any document is always imported to the latest
development release and when saved it is done in the stable file
format.

On the other hand what this would mean to stress the
conversion/reversion round trip.

This could be implemented as some kind of option to set, by default,
the save file format version or even better, because in this case this
is what it intended, the target version.

In the preferences file this could go as:

\save_file_format 2.4

If this option is not set then everything works as usual.
If it is set then, when the file is saved, the file is reverted to that
file format.

I hope that this idea helps, :-)
-- 
José Abílio
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: File format increases on master make it hard to test

2024-04-07 Thread Scott Kostyshak
On Sun, Apr 07, 2024 at 06:32:47AM GMT, Jürgen Spitzmüller wrote:
> Am Samstag, dem 06.04.2024 um 16:51 -0400 schrieb Scott Kostyshak:
> > I imagine others face the same situation? Is there anything that can
> > be done?
> 
> No, I think this will be a nightmare to maintain. And then, you really
> do not "text master" if you strip the most interesting commits.

Fair enough. That was what I was afraid of (and expected).

Scott


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


Re: File format increases on master make it hard to test

2024-04-06 Thread Jürgen Spitzmüller
Am Samstag, dem 06.04.2024 um 16:51 -0400 schrieb Scott Kostyshak:
> I imagine others face the same situation? Is there anything that can
> be done?

No, I think this will be a nightmare to maintain. And then, you really
do not "text master" if you strip the most interesting commits.

-- 
Jürgen


signature.asc
Description: This is a digitally signed message part
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


File format increases on master make it hard to test

2024-04-06 Thread Scott Kostyshak
I've been enjoying testing master, but on the first file format increment, I'll 
stop a lot of my testing since they're documents I will want to work on with 
other people.

I have a few documents that only I use and for that I'll try to continue to 
test master.

I imagine others face the same situation? Is there anything that can be done? I 
remember that Guillaume used to maintain a lyx-unstable (I think this was the 
name) where I think he removed the file format updates. How hard would that be 
to maintain?

I guess ideally anything that doesn't involve a file format bump would also 
eventually be pushed to 2.4.x, so our testing of 2.4.x should help indirectly 
to test master, but there are a lot of commits that don't go to 2.4.x (for good 
reason). I guess an alternative would be to have a master-no-file-format 
branch, that gets all the commits master does except file format increments? 
But in this case it seems it would be less work to maintain the lyx-unstable 
referenced above, so that we don't have to double-commit each time?

Not sure if anything can feasibly be done here, but wanted to ask.

Scott


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