Re: Help testing release candidate / mc-4.8.24-rc1

2020-01-07 Thread wwp
Hello Andrew,


On Tue, 07 Jan 2020 17:45:28 +0300 Andrew Borodin  wrote:

> On Tue, 7 Jan 2020 14:15:21 +0100 wwp wrote:
> > I think I have one more tiny issue to report.. I went back to 4.8.23,
> > and at least two settings from the layout prefs were lost: command
> > prompt and panel split. Maybe you changed the storage format for some
> > config items?  
> 
> Yes. This is a result of [1].
> 
> Previously some options that are actually boolean were stored
> as intreger 0/1. Now its are stored as yes/no.
> 
> [1] https://midnight-commander.org/ticket/4039

Thanks, this all makes sense now!


Regards,

-- 
wwp
https://useplaintext.email/


pgp5lWsce_9ki.pgp
Description: OpenPGP digital signature
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Re: Help testing release candidate / mc-4.8.24-rc1

2020-01-07 Thread Andrew Borodin
On Tue, 07 Jan 2020 17:45:28 +0300 Andrew Borodin wrote:
> On Tue, 7 Jan 2020 14:15:21 +0100 wwp wrote:
> > I think I have one more tiny issue to report.. I went back to 4.8.23,
> > and at least two settings from the layout prefs were lost: command
> > prompt and panel split. Maybe you changed the storage format for some
> > config items?
> 
> Yes. This is a result of [1].
> 
> Previously some options that are actually boolean were stored
> as intreger 0/1. Now its are stored as yes/no.

Sorry. Not yes/no, but true/false.

> 
> [1] https://midnight-commander.org/ticket/4039

-- 
А.
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Re: Help testing release candidate / mc-4.8.24-rc1

2020-01-07 Thread Andrew Borodin
On Tue, 7 Jan 2020 14:15:21 +0100 wwp wrote:
> I think I have one more tiny issue to report.. I went back to 4.8.23,
> and at least two settings from the layout prefs were lost: command
> prompt and panel split. Maybe you changed the storage format for some
> config items?

Yes. This is a result of [1].

Previously some options that are actually boolean were stored
as intreger 0/1. Now its are stored as yes/no.

[1] https://midnight-commander.org/ticket/4039

-- 
А.
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Re: Help testing release candidate / mc-4.8.24-rc1

2020-01-07 Thread wwp
Hello Yury,


On Wed, 01 Jan 2020 21:02:50 +0100 "Yury V. Zaytsev"  wrote:

> Hi there,
> 
> TLDR; I would appreciate if you could please test the following tarball
> on your systems and report any blocker regressions as compared to the
> previous 4.8.23 release: 
> 
> https://www.midnight-commander.org/nopaste/tarball/mc-4.8.23-149-g06bf088bc.tar.xz
> 
> $ sha256sum mc-4.8.23-149-g06bf088bc.tar.xz
> bafd8a0556504c2806b77cd7506ac087d4ad050fbb4d711fbd7898fe493493fd  
> mc-4.8.23-149-g06bf088bc.tar.x
> 
> I've built this tarball out of the latest master with translations from
> Transifex pulled in on a fresh Fedora 31 VM, which I'm also going to use
> to build the final release in about a week from now if nothing serious

I think I have one more tiny issue to report.. I went back to 4.8.23,
and at least two settings from the layout prefs were lost: command
prompt and panel split. Maybe you changed the storage format for some
config items?


Regards,

-- 
wwp
https://useplaintext.email/


pgpnVHJW5XLux.pgp
Description: OpenPGP digital signature
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Re: Help testing release candidate / mc-4.8.24-rc1

2020-01-06 Thread wwp
Hello Andrew,


On Mon, 06 Jan 2020 16:18:32 +0300 Andrew Borodin  wrote:

> On Mon, 6 Jan 2020 12:45:57 +0100 wwp  wrote:
> > 
> > I noticed one regression: if I start mc, then start mcedit from
> > subshell, I'll get:
> > ===
> > GNU Midnight Commander is already running on this terminal.
> > Subshell support will be disabled.
> > ===
> > 
> > Back to 4.8.23 and the issue is gone, as expected.  
> 
> Notice if you run standalone mceditor, you haven't a subshell in it [1].
> 
> A new behavior (I can't say this is a bug) is a some kind of payment 
> for having a full-functional subshell in standalone 
> mceditor/mcviewer/mcdiffviewer.
> Now if you run mcedit from mc it is the same as you run mc from mc
> with all features.
> 
> [1] https://midnight-commander.org/ticket/3380

Maybe not a bug, but the error message is quite useless and pretty
nagging, IMO, in addition of behaving differently than formerly.


Regards,

-- 
wwp
https://useplaintext.email/


pgpBsc3bEZiLq.pgp
Description: OpenPGP digital signature
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Re: Help testing release candidate / mc-4.8.24-rc1

2020-01-06 Thread Andrew Borodin
On Mon, 6 Jan 2020 12:45:57 +0100 wwp  wrote:
> 
> I noticed one regression: if I start mc, then start mcedit from
> subshell, I'll get:
> ===
> GNU Midnight Commander is already running on this terminal.
> Subshell support will be disabled.
> ===
> 
> Back to 4.8.23 and the issue is gone, as expected.

Notice if you run standalone mceditor, you haven't a subshell in it [1].

A new behavior (I can't say this is a bug) is a some kind of payment 
for having a full-functional subshell in standalone 
mceditor/mcviewer/mcdiffviewer.
Now if you run mcedit from mc it is the same as you run mc from mc
with all features.

[1] https://midnight-commander.org/ticket/3380

-- 
Andrew
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Re: Help testing release candidate / mc-4.8.24-rc1

2020-01-06 Thread wwp
Hello Yury,


On Wed, 01 Jan 2020 21:02:50 +0100 "Yury V. Zaytsev"  wrote:

> Hi there,
> 
> TLDR; I would appreciate if you could please test the following tarball
> on your systems and report any blocker regressions as compared to the
> previous 4.8.23 release: 
> 
> https://www.midnight-commander.org/nopaste/tarball/mc-4.8.23-149-g06bf088bc.tar.xz
> 
> $ sha256sum mc-4.8.23-149-g06bf088bc.tar.xz
> bafd8a0556504c2806b77cd7506ac087d4ad050fbb4d711fbd7898fe493493fd  
> mc-4.8.23-149-g06bf088bc.tar.x
> 
> I've built this tarball out of the latest master with translations from
> Transifex pulled in on a fresh Fedora 31 VM, which I'm also going to use
> to build the final release in about a week from now if nothing serious
> comes up. 

I noticed one regression: if I start mc, then start mcedit from
subshell, I'll get:
===
GNU Midnight Commander is already running on this terminal.
Subshell support will be disabled.
===

Back to 4.8.23 and the issue is gone, as expected.


GNU Midnight Commander 4.8.23-149-g06bf088bc
Built with GLib 2.56.1
Using the S-Lang library with terminfo database
With builtin Editor and Aspell support
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
Virtual File Systems: cpiofs, tarfs, sfs, extfs, ftpfs, sftpfs, fish, smbfs
Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;



Regards,

-- 
wwp
https://useplaintext.email/


pgpsYvUgow6br.pgp
Description: OpenPGP digital signature
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Help testing release candidate / mc-4.8.24-rc1

2020-01-01 Thread Yury V. Zaytsev
Hi there,

TLDR; I would appreciate if you could please test the following tarball
on your systems and report any blocker regressions as compared to the
previous 4.8.23 release: 

https://www.midnight-commander.org/nopaste/tarball/mc-4.8.23-149-g06bf088bc.tar.xz

$ sha256sum mc-4.8.23-149-g06bf088bc.tar.xz
bafd8a0556504c2806b77cd7506ac087d4ad050fbb4d711fbd7898fe493493fd  
mc-4.8.23-149-g06bf088bc.tar.x

I've built this tarball out of the latest master with translations from
Transifex pulled in on a fresh Fedora 31 VM, which I'm also going to use
to build the final release in about a week from now if nothing serious
comes up. 

Many thanks!

-- 
Sincerely yours,
Yury V. Zaytsev



signature.asc
Description: This is a digitally signed message part
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel