Thanks to Egmont and everyone else who has reported regressions so far, and to
Andrew for fixing them! I hope that this way we are going to be able to make a
solid release on the weekend...
Sent from my iPad
> On 18. Jun 2019, at 09:16, Egmont Koblinger wrote:
>
> Thanks for the quick fix!
>
Thanks to Egmont and everyone else who has reported regressions so far, and to
Andrew for fixing them! I hope that this way we are going to be able to make a
solid release on the weekend...
Sent from my iPad
> On 18. Jun 2019, at 09:16, Egmont Koblinger wrote:
>
> Thanks for the quick fix!
>
Thanks for the quick fix!
I've verified the behavior after an F9. (I didn't do an extensive
walkthrough of the UI, I hope you're confident that shortcuts work
everywhere else too as expected :))
egmont
On Tue, Jun 18, 2019 at 8:38 AM Andrew Borodin wrote:
>
> On Mon, 17 Jun 2019 22:56:45 +0200
On Mon, 17 Jun 2019 22:56:45 +0200 Egmont Koblinger via mc-devel wrote:
> There's a severe usability regression: After pressing F9 the hotkeys
> (e.g. O for Options, then L for Layout) don't work.
Thanks for the bugreport.
Fixed in 7eaa51c79bb74e6e650935e23895c62073ff46c5.
--
A.
On Mon, 17 Jun 2019 22:56:45 +0200 Egmont Koblinger via mc-devel wrote:
> There's a severe usability regression: After pressing F9 the hotkeys
> (e.g. O for Options, then L for Layout) don't work.
Thanks for the bugreport.
Fixed in 7eaa51c79bb74e6e650935e23895c62073ff46c5.
--
A.
git bisect points to f5f78ea658 "Ticket #212: implement keybinding for menu."
e.
On Mon, Jun 17, 2019 at 10:56 PM Egmont Koblinger wrote:
>
> Hi guys,
>
> There's a severe usability regression: After pressing F9 the hotkeys
> (e.g. O for Options, then L for Layout) don't work.
>
> cheers,
>
Hi guys,
There's a severe usability regression: After pressing F9 the hotkeys
(e.g. O for Options, then L for Layout) don't work.
cheers,
egmont
On Sun, Jun 16, 2019 at 9:14 PM Yury V. Zaytsev wrote:
>
> Hi there,
>
> TLDR; I would appreciate if you could please test the following tarball
> on
On 17/06/2019 16:42, Henning wrote:
Build and run ok on CYGWIN_NT-6.3 3.1.0s(0.338/5/3) 2019-06-05 i686.
Just build (and run) ok from master. Warnings about shadowed
declarations are gone, but 'mc --version' gives 'unknown'.
Henning
___
On 16/06/2019 20:56, Yury V. Zaytsev wrote:
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.22 release:
Build and run ok on CYGWIN_NT-6.3 3.1.0s(0.338/5/3) 2019-06-05 i686.
Warnings
On Mon, 17 Jun 2019 08:56:55 +0200 David Martin via mc-devel wrote:
> "Ubuntu 16.04.6 LTS": many unsigned int cast warnings for smbfs.
Thanks for the report.
Fixed in
c47f0c4bba7af48c2147950f23fbc2e14f1de162
92146f10333f6068d6b0a54921bd2cae284705a7
--
Andrew
"Ubuntu 16.04.6 LTS": many unsigned int cast warnings for smbfs.
LDFLAGS=-s ./configure --with-x --enable-aspell --enable-vfs-undelfs
--enable-vfs-smb --disable-doxygen-doc --enable-aspell
...
ar: `u' modifier ignored since `D' is the default (see `U')
...
ar cr libsamba.a
On Sun, 16 Jun 2019 22:06:56 -0600 Jack Woehr via mc-devel wrote:
> make[4]: Entering directory '/usr/local/src/MC/build-4.8.22-166/src/vfs/sfs'
> CC sfs.lo
> ../../../../mc-4.8.22-166-gcd16697a3/src/vfs/sfs/sfs.c: In function
> ‘sfs_open’:
>
Hope this is useful. Ran a quick build and test and seems to build and run
okay on Ubuntu 18.04.2 LTS
Warning-level glitches in build:
CCLD seems always to end with warning ar: `u' modifier ignored since `D' is
the default (see `U')
Building vfs:
Making all in sfs
make[4]: Entering directory
13 matches
Mail list logo
