Re: Quick view
On Sun, 2 Oct 2022, Andrew Borodin wrote:
- Directories show the string "Cannot view: not a regular file" but it
might be a good feature to show the contents, or maybe a short
description of it ("X images, Y documents")
Again, to calculate directory statistics, or get some info of file, we
need some time. Any delay can annoy users.
Well, I vaguely remember that FAR had such a feature, and it was pretty
nice. One should just think of stuff we can show fast and keep in mind VFS
limitations...
--
Sincerely yours,
Yury V. Zaytsev
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.28 released
On Mon, 28 Mar 2022, Joseph Reagle wrote: Hi, I've looked in the release notes, but I don't see anything related to reopening [4198]? Why would there be anything regarding reopening this ticket in the release notes? The support for zsh is unfortunately flakey since a couple of releases already. There is an open ticket #3121, which I mentioned in #4198, but my answer was ignored so far. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.28 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I'm glad to announce the immediate availability of mc-4.8.28, a maintenance and bugfix release! We have fixed number of bugs in various subsystems, most notably a long-standing problem of mc being slow when moving large file trees (thanks to Sergei Trofimovich!). Other than that, we have finally completely removed half-broken, outdated and insecure SMB support. We recommend using one of the many current VFS solutions to work with Windows shares instead. For a detailed list of changes since the last release, please refer to the release notes. An upgrade is advised to benefit from these improvements! Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.28 Unfortunately, Apple M1 is still not supported directly, the necessary changes will hopefully make it in Fedora 36, which we will be able to use as a build system for the next release. Until then, please re-bootstrap the build system on Mac or use the following workaround: CFLAGS="-target arm64-apple-macos12" \ ./configure \ --host=aarch64-apple-darwin \ --target=aarch64-apple-darwin \ --build=aarch64-apple-darwin As usual, thanks to Andrew Borodin, who was the main driving force behind this release, as well as all of our contributors, including translators. Have fun with this new release! Z. - -- Sincerely yours, Yury V. Zaytsev -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJiQGOAAAoJEPci7nm8u+DvpgkQAIAFWAxHrvq/JicDkRKGT8fg 9HvTuVddGtGD1jFkSp50zJXmVZDBZCI+Yn+/q0AYPvutpgwYt2fGtQRVmlWvNfmW vI3zF9VlAgLx5tsvYXeKnM4qP18xh8V7CQO4Ndkf85kf6kAhRddYcxuHOP5oq9Gg vboLr59Bp6qsGMwpSQOMymdBYNbYarC1yJZ+nmabT2mqL1VUArqnm/XYdtYwR0ef Vm5S9OQKysnPJcdR68+I0SZYQdA3wCaCWTRNnLsay4ofdtY/w+OktHteVWnDdpK2 Qkb+QuV6E4ZacTcNRCp28s19gAXoLsVuqMqSMzDfMvNnbnBz6xTPdNjoA1BhyY2K 45RUJCdEy+LNOSlq8gX5Y12GXsArbkTn6935rUSlHUaZmYnfpWYT5k9wP/c++Orc khpI0YZKBpo2qiale3mO0CsG9wp6ARy6g+dokheHcevL8/4tkdWe8lYIEXXUf8QL +M+CKOBuSMxy2H7w+k7lB1jFyUld+aLztz7Gypjqnu+lJ8i2+0+tWnsTOLLiNFkp d9YM7t85JSgS7pij7yPvMdlUE318A85gZOFJjgc50MMRLMKkTuiQwDBPnUGaw8Hr 5YHLD1hfzJU6iMTE2lpLctmMcS6NjeCKJ8WrxmXdquM/m11OjZRLHE7C+xyxqABK z5f6PVvRfiJWIlFVJEmK =xj+I -END PGP SIGNATURE- ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing release candidate / mc-4.8.28-rc1
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.27 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.28-pre1.tar.xz $ sha256sum mc-4.8.28-pre1.tar.xz e6b0423e47225e78fb59968cc45c0b004676a17ab45d7f304a091121326bfb77 mc-4.8.28-pre1.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 35 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 ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Fwd: Try to wrap Midnight Commander in Rust
On Tue, 17 Aug 2021, Enrico Weigelt, metux IT consult wrote: Why building rust code in mc at all ? Do you wanna rewrite mc in rust ? Then you'd better start completely afresh. (and give it a different name). He did give it a different (working) name - mc-rs - he's published his experiment on his own GitHub account and has invited anyone who is interested to contribute. All fine by me... Since the original post contained questions about compiler warnings pertaining to the mc source code, I have forwarded it to this list, where it was quickly and helpfully answered. If you have important opinions to share on Rust, please find a different forum for this though. But before you do, I'd urge you to rethink whether this is necessary in the first place... Vitold is like anyone else entitled to use his time however he wants, and if he set out to rewrite mc in Rust, it's up to him to decide whether he should do it incrementally or by starting from scratch. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.27 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I'm glad to announce the immediate availability of mc-4.8.27, a maintenance and security release, just in time before leaving all of you for a long overdue summer vacation! This release addresses an important security issue (CVE-2021-36370) in the SFTP VFS. Unfortunately, as the VFS was first introduced, the fingerprints of remote hosts were computed, but not verified, and the issue reported only now by Manfred KAISER from AUT-milCERT during an audit of open source software. We would like to thank the team at AUT-milCERT for finding the issue and responsibly disclosing it! Other than that there is a large slew of assorted bugfixes to various subsystems. For the detailed list of changes since the last release, please refer to the release notes. Everybody is recommended to upgrade to immediately benefit from these improvements! Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.27 Unfortunately, the autotools support for Apple M1 has not propagated widely enough, so if you need to build mc on such a system, you will have to specify the triplets manually - hopefully this will be no longer necessary by the time of the next release: CFLAGS="-target arm64-apple-macos11" \ ./configure \ --host=aarch64-apple-darwin \ --target=aarch64-apple-darwin \ --build=aarch64-apple-darwin As usual, thanks to Andrew Borodin, who was the main driving force behind this release, as well as all of our contributors, including translators. Have fun! - -- Sincerely yours, Yury V. Zaytsev -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJhGSZwAAoJEPci7nm8u+Dv7tUP/3UZEBUrTcCoY5I6p+9jTZni 2EXvl3qWuKK+2F0WOpztNAct0b6kyMOqtfH2VsRB6Set/8vhY9bx6b48cnZhkUR0 WTlmGq/eK1KTYfac7oYwp7RfknJ4jS99MdJXKUu9tukTD/QP+iBURhC+xTnh/yrJ fzWn6UEsvHvDoHDFyZi0C8UYIbCd+XNyaxQNtJANf8SAwAtzTEcvhs63DX6DAJm2 uARL1EiKT2D0HCELSRhEAH+XwYEkd+4N8nWBaB1mo3TditY7bbFW/c+TV+Z78Cxq p2RsoAhEDSPAyPBYpzXvYwQ2OgX56ug+wKMqjlYWtTYSC+Z6jqtZhYb2Mg9beY8e B6gE5w9h//UA7zPqt01+LN4ErdHUyUejpk6eBYX7z/RABaURGZ41GaCEnxhcULnZ lwOzU19puEFRIG5L1gXAr5KiTTh5/ALdn7OyxrXIVd4HRosFXSbZVwCAcWPdL2uj 17Na5volVN1VSD225/RJ8BnP0PWNxPlnpfSUEHJnaz0FWrwgE3oHHvMmkPQ6JbOP ap0uZZyebtaUBHLL3gvriu/SKTWvT/VMGgbDi660mN5pKYgtbYDzqjy4SR38hQmX 27xD6pKFIFM7kQReeqc6sXq+SckuMYs2rpmDYVlj/eIacqAWPArTgDuWZ/sqbS+e /6JHh/vU7I1JxZXmfl5o =qJEm -END PGP SIGNATURE- ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Fwd: Try to wrap Midnight Commander in Rust
Hi Vitold,
Please don’t contact us using our private addresses, we don’t have the capacity
to provide personal support for mc. I have forwarded your message to the
development mailing list, maybe Andreas could have a look at this before next
release…
Sent from my iPad
Begin forwarded message:
> From: Vitold S
> Date: 15. August 2021 at 06:10:30 CEST
> To: y...@shurup.com
> Subject: Try to wrap Midnight Commander in Rust
>
>
> Hello,
>
> I am was try to make Rust wrapper for Midnight Commander in
> https://github.com/vit1251/mc-rs
>
> Since I start I receive a lot of warning message:
>
> warning: lib/event/manage.c: In function ‘mc_event_group_destroy_value’:
> warning: lib/event/manage.c:52:37: warning: cast between incompatible
> function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’
> [-Wcast-function-type]
> warning:52 | g_ptr_array_foreach (callbacks, (GFunc) g_free, NULL);
> warning: | ^
> warning: lib/event/manage.c: In function ‘mc_event_get_event_group_by_name’:
> warning: lib/event/manage.c:169:30: warning: cast between incompatible
> function types from ‘gint (*)(const gchar *, const gchar *)’ {aka ‘int
> (*)(const char *, const char *)’} to ‘gint (*)(const void *, const void *,
> void *)’ {aka ‘int (*)(const void *, const void *, void *)’}
> [-Wcast-function-type]
> warning: 169 | g_tree_new_full ((GCompareDataFunc)
> g_ascii_strcasecmp,
> warning: | ^
> warning: lib/event/event.c: In function ‘mc_event_init’:
> warning: lib/event/event.c:62:26: warning: cast between incompatible function
> types from ‘gint (*)(const gchar *, const gchar *)’ {aka ‘int (*)(const char
> *, const char *)’} to ‘gint (*)(const void *, const void *, void *)’ {aka
> ‘int (*)(const void *, const void *, void *)’} [-Wcast-function-type]
> warning:62 | g_tree_new_full ((GCompareDataFunc)
> g_ascii_strcasecmp,
> warning: | ^
> warning: lib/filehighlight/common.c: In function ‘mc_fhl_array_free’:
> warning: lib/filehighlight/common.c:61:44: warning: cast between incompatible
> function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’
> [-Wcast-function-type]
> warning:61 | g_ptr_array_foreach (fhl->filters, (GFunc)
> mc_fhl_filter_free, NULL);
> warning: |^
> warning: lib/search/search.c: In function ‘mc_search__conditions_free’:
> warning: lib/search/search.c:121:33: warning: cast between incompatible
> function types from ‘void (*)(mc_search_cond_t *)’ {aka ‘void (*)(struct
> mc_search_cond_struct *)’} to ‘void (*)(void *, void *)’
> [-Wcast-function-type]
> warning: 121 | g_ptr_array_foreach (array, (GFunc)
> mc_search__cond_struct_free, NULL);
> warning: | ^
> warning: lib/strutil/replace.c: In function ‘str_replace_all’:
> warning: lib/strutil/replace.c:112:39: warning: cast between incompatible
> function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’
> [-Wcast-function-type]
> warning: 112 | g_ptr_array_foreach (str_splints, (GFunc) g_free, NULL);
> warning: | ^
> warning: lib/widget/group.c: In function ‘group_default_callback’:
> warning: lib/widget/group.c:580:37: warning: cast between incompatible
> function types from ‘void (*)(Widget *)’ to ‘void (*)(void *, void *)’
> [-Wcast-function-type]
> warning: 580 | g_list_foreach (g->widgets, (GFunc) widget_destroy,
> NULL);
> warning: | ^
> warning: src/filemanager/boxes.c: In function ‘appearance_box’:
> warning: src/filemanager/boxes.c:665:38: warning: cast between incompatible
> function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’
> [-Wcast-function-type]
> warning: 665 | g_ptr_array_foreach (skin_names, (GFunc) g_free, NULL);
> warning: | ^
> warning: src/filemanager/treestore.c: In function ‘tree_store_notify_remove’:
> warning: src/filemanager/treestore.c:483:34: warning: cast between
> incompatible function types from ‘void (*)(void *)’ to ‘void (*)(struct
> tree_entry *, void *)’ [-Wcast-function-type]
> warning: 483 | tree_store_remove_fn r = (tree_store_remove_fn)
> p->hook_fn;
> warning: | ^
> warning: src/filemanager/treestore.c: In function
> ‘tree_store_add_entry_remove_hook’:
> warning: src/filemanager/treestore.c:665:36: warning: cast between
> incompatible function types from ‘tree_store_remove_fn’ {aka ‘void (*)(struct
> tree_entry *, void *)’} to ‘void (*)(void *)’ [-Wcast-function-type]
> warning: 665 | add_hook (_entry_hooks, (void (*)(void *))
> callback, data);
> warning: |^
> warning: src/filemanager/treestore.c: In function
>
Re: Help testing release candidate / mc-4.8.27-rc1
On Tue, 3 Aug 2021, Andreas wrote: This can happen if configure and build step run with different compiler. At configure step (exactly at mc-cflags.m4) compiler flags are tested against compiler support, if supported it will added to build/make config. Thanks for the tip! Maybe setting the compiler in my command is actually not necessary and only causes those warnings? Joseph, could you please try a clean build without setting "CC"? Thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Help testing release candidate / mc-4.8.27-rc1
On Mon, 2 Aug 2021, Joseph Reagle wrote: I ran the command you suggested and the make, make install, creates a binary in /usr/local/bin (though using homebrew arm64 commands in /opt/homebrew) and it seems to work fine. Thanks for the confirmation! Then specifying triplets manually on Apple Silicon will be the workaround I will put in the release notes, until we get proper autotools support (hopefully) with the next release. If you are unhappy with /usr/local, you can always specify custom prefix with --prefix=$HOME/opt/mc or so. (It doesn't include panel scrollbars from #4256?). Unfortunately, the author disappeared as suddenly as he appeared and the patch was left unfinished - thus it will not make it in this release. BTW: During make, I get tons of warnings: warning: unknown warning option '-Wformat-signedness' [-Wunknown-warning-option] warning: unknown warning option '-Wmaybe-uninitialized'; did you mean '-Wuninitialized'? [-Wunknown-warning-option] warning: unknown warning option '-Wmissing-parameter-type' [-Wunknown-warning-option] warning: unknown warning option '-Wunused-but-set-variable'; did you mean '-Wunused-const-variable'? I've put our chief warning officer on CC, hopefully he can say something about that - apparently our compiler flag detection is not working correctly and warning flags are supplied even though they are not supported by the compiler... Could you please post the complete build log as a compressed attachment? -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Help testing release candidate / mc-4.8.27-rc1
On Mon, 2 Aug 2021, Joseph Reagle wrote: I tried but: ``` ... checking build system type... Invalid configuration `arm64-apple-darwin20.6.0': machine `arm64-apple' not recognized configure: error: /bin/sh config/config.sub arm64-apple-darwin20.6.0 failed ``` Hi Joseph, Oh noes, you seem to be running Apple Silicon and the autotools in Fedora Rawhide do not support it yet. Could you please try specifying the triplets by hand? If this works, then this would be the workaround until newer autotools propagate to major Linux distributions - I would be very scared of bootstrapping the official tarballs on macOS with custom Apple-patched autotools... $ CC="/usr/bin/cc" \ CFLAGS="-target arm64-apple-macos11" \ ./configure \ --host=aarch64-apple-darwin \ --target=aarch64-apple-darwin \ --build=aarch64-apple-darwin Thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing release candidate / mc-4.8.27-rc1
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.26 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.27-pre1.tar.xz $ sha256sum mc-4.8.27-pre1.tar.xz d922e4175a20779549c4a9746bbe169d4acd2a83b2e14d1d6dfd2cbec32eb12b mc-4.8.27-pre1.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 33 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 ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Help testing release candidate / mc-4.8.26-rc1
On Mon, 11 Jan 2021, Sergei Trofimovich wrote: Is there an option to tag release candidates just like releases and name/upload tarballs into expected locations just like releases? Hi Sergei, Yes, I can do this in the future if this would make your life easier - I just took over the process from Slava and never realised that it might be inconvenient for maintainers, after we decided to distribute internal test builds as rcs before release to get a bit more coverage. What should the tags look like? 4.8.27-rc1 -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.26 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, After a spectacularly crappy year 2020, I'm glad to announce the immediate availability of mc-4.8.26, this time with a couple of new particularly awesome features! The major highlight of this release is without doubt the support for persistent subshell buffer contributed by Eric Roberts with fixes by Oswald Buddenhagen. How many times did you start typing something after hiding the panels, then switched the panels on and off again just to find your text erased, garbled or even incorrectly executed? Not anymore! Have you been missing the eye candy of the good old Turbo Vision shadows? It took a few decades, but thanks to Aleš Janda you can finally enjoy them in mc (or you can turn them off, it's not your cup of tea). Other than that, mc now supports arbitrary long filenames, directory listing on CIFS mounts should work correctly again on latest kernels, among many other smaller fixes of that sort. Everybody is recommended to upgrade to immediately benefit from these improvements! For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.26 As usual, thanks to Andrew Borodin, who was the main driving force behind this release, as well as all of our contributors, including translators. Stay healthy! - -- Sincerely yours, Yury V. Zaytsev -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJgCcOBAAoJEPci7nm8u+Dvjn4QAJQdPNHjK0sF3FncqNR36Qm7 P/Qk9QJ1VvjVpAhJG5POaAMVCOpsLVvUEVrMMyHMiSP8Gh8Md61nYAj6YpvI9dsG +jCGLsogLgOqGPsnT0PGuQLiOquAQuc53Fr1Fm728P9T26/Q9SruSQvyUU9CeRCA IKaZBJukv1/CejtpaHl4t2MZLQKdyijYZFxXdFUw6Dq83ITBgxO/xpdg+mD52BXJ LkKd9sV8bjS/bdRXtm2wIZZVhpaa5Fo6eHJAKR+iv4OFNMq4+7C6rs4j+kgzJowS OMQIUSR0eJslDMmns+mz2a+w8zja4b2DMaMODouz27yiCSNw9xTniy3oqKuejGr/ xxSdoMcDSnCNDCWkUVpTO9bPC2Izgx8N+FiQut/m9EKZhbqsXoYJN0lYhGjfTzmM 7MT9GG4anvifFQwah57CBl88osZryuClQLOtoPmkAvdmFFNFopfxLEvOAMCMQdDV rzUBkBEUg5rRsCspBmbMy1dZc9AG1X4g3PKiUguJW+YFfmnnmLPQtdXZPi+urt6t 7A2WP9kEgHIRTcQDBA89zYmgHKNtRDS64fFkOKtolUlb1z/GVFXZva4IJwUH4ZIK Xfp/q7Ev4/yA2xwtt0dVq0aJGCGlUCGaN3H9gZpfpVdfls9c6SZa/DtqNAL34fAG GAevkLjAqbg6mGFkWcOz =qn6x -END PGP SIGNATURE-___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing release candidate / mc-4.8.26-rc1
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.25 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.25-154-g33c84e75e.tar.xz $ sha256sum mc-4.8.25-154-g33c84e75e.tar.xz ce5f965a9be603098eda65afd1aa149e285d903fe303fe907c6a5e88f28dd772 mc-4.8.25-154-g33c84e75e.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 33 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 ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.25 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm glad to announce the immediate availability of mc-4.8.25! This is a maintenance release including several new features and fixes for issues found since the last one. It is now possible to change file attributes via a graphical dialog, just like file permissions. Key bindings for radio buttons can now be redefined. Annoying subshell warning when launching standalone editor & viewer should be finally gone. Other than that, a number of changes and fixes have taken place touching various components such as the build system, syntax definitions and so on. Everybody is recommended to upgrade to immediately benefit from these improvements! For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.25 As usual, thanks to Andrew Borodin, who was the main driving force behind this release, as well as all of our contributors, including translators. Enjoy the summertime! - -- Sincerely yours, Yury V. Zaytsev -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJfEzXxAAoJEPci7nm8u+DvozsP/iRKc6CSN2k5EcDC35DOvjFv KnWmgCm/qmrPowSZRfDZLMcyC4tM3Jj9++s0iXdXFwFVqLcnVl3X5avKRvelmTYP D4O8AVDM2KCdYMIFjDdomSPNF1P/vjNefOUp4ikaLSCYOGVgqrfml3q+LSPm7IjS KzXOXg/I7rBCUmURT/UUDC+dK6djdorXjN2exx/pnIrcwmrFbNpyKejMpZQ/ke+o ApOhQvhq/uezGf6RLFaFzfJIMe6yJFrW3sCmpMM8p2g2KDGMqSIOkvOyMfF41t6h FOg/fNbcAKsoY8KlJzXqlTtDoVs/jYOB2G4AmSJTU4wZHw3sBiwNr2MdpKyeRuN3 yyWCtzzMTW7rO8w6+vKtXqolCH67XNoH+umQ6KxssJlFiqDNgdq5hDI8G38WkI+Q DrOBeEzOjUmnET3foovnRLwTRMMxFXis0Bdm4RvUgVZ7da/h1zgFA+BM/iByQ7Zt ghZqKEI3zdUOuuVhSp4KNafUIDCv/vwXbHX7Euzd3QkFI2+YEwFnEH/CzaoGVer5 lhFTDHK4a8el8zM6PKtp5ByOJdCAuFI+FNQF1dC5hD1OKqCTg0bjI4DE3gDWYaCW /XcC54RD4qq6MqT1t+1cJg5nIgj9ZUOp3VBuK59eRy+5g5jOXhf0YDWE6pIi3BDq CXhuw7kvre7VmgWVIb4Q =PaB8 -END PGP SIGNATURE- ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing release candidate / mc-4.8.25-rc1
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.24 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.24-163-g171957980.tar.xz # sha256sum mc-4.8.24-163-g171957980.tar.xz 68619d24d893d0314301e5b218f7fa1abbdc907556ffaa6465daa251ced073ec mc-4.8.24-163-g171957980.tar.xz 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 ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] Initialize struct stat st_[acm]tim.tv_nsec when present
On Thu, 21 May 2020, Nerijus Baliūnas wrote: I thought he was a Fedora mc package maintainer, but it seems I confused him with someone else, sorry! I see, maybe you confused Egmont with Jindřich Nový? He used to maintain mc in Fedora, but I don't know if he's active these days - haven't met him for many years :-( Anyways, your best bet would be to open a ticket in RH bugzilla - we can't help you here. -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] Initialize struct stat st_[acm]tim.tv_nsec when present
On Tue, 19 May 2020, Nerijus Baliunas via mc-devel wrote: Unfortunately, mc 4.8.20 was released only in half a year after May 2017 (November 2017), and it was not included in RHEL 8 (that's the main reason I was asking to make a release sooner). The version in RHEL/CentOS 8 has that annoying bug with not preserving timestamps. Egmont, is there a possibility to release an updated mc package for RHEL 8? Hi Nerijus, Why in the world you would be asking Egmont about that :) ? In as far as I know, he's never worked for RH or maintained mc RPM packages. If you use RHEL, just open a support ticket, asking them to upgrade mc or backport the timestamp patch to mc 4.8.19... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.24 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm glad to announce the immediate availability of mc-4.8.24! This is a maintenance release including several new features and fixes for issues found since the last one. The most interesting improvements that landed in this release are the new file view & edit history and a fully functional subshell in standalone editor and viewer. Apart from that a number of bugfixes and improvements have taken place touching various components such as the build system, syntax definitions and so on. Everybody is recommended to upgrade to immediately benefit from these improvements! For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.24 As usual, thanks to Andrew Borodin, who was the main driving force behind this release, as well as all of our contributors, including translators. Unfortunately, this release got a bit delayed by a nasty cold, but I would still like to wish you all a Happy New Year 2020, even if it's a bit late! - -- Sincerely yours, Yury V. Zaytsev -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJeJIfyAAoJEPci7nm8u+DvkhEQAKGdtG1KnfyQPybEV80nZi9O WAITmKOHCMLIww/hx7YNTr2R74RbdmW5SaqDACp2erC1TREkejM4KdnbhDxIsCHE qZ9lMo7nlF9FpKAGyjA3+azTbRhxVTgOWBsS9sIYfH48abZ7gcxhIdaqRK5KHnVn XWr7vdjSPQmVlf9bmHpFGk3quLPtHpg/A9riEVzNxoZhxuWpdBRtL6xrXcCmFnFE 9tBl4tplXST+uATeG61oP/FFdNHD0waoWFuEbGuLXNWmDNTvurBGyLNnz/cd5DMv /3zL/EMV4hPUs6TOuGTlo8sXwnzlzGwe95U2UEhRKGVv/0b/luXRPvP9gF41/zNI xKeQb6sfiqVptKlIPTzoQ/X+LaP1wNQo5el2ZU4FP9v+zDDOFzKs16x4wk/TS9i0 VPglz5qdBjZjwI0XjitxoA1olJd2xiCV8A6VRFmgcB4tATcr0ppkw6qXEuBYcn5r 7CTaihneQfyu/OmpjMhMfMQLqVjCX4r5aZonM50DcCzQ1g32FUz2V7otnkBJEcQi kV9nJ2L7+B95Ox0RN5IXT41AgEa0o98gPOryYMoygNyERvfNz/HzAMTbTK7g6xPN tRwAtnJL+gFILz32zYXVpGBjyzz8C8BAf+p7daLdHxlmJPJ/MAFhyj7mZiBWIBTS XEMv9ZlzG2XuKJxscEZu =dW8t -END PGP SIGNATURE- ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing release candidate / mc-4.8.24-rc1
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
Midnight Commander 4.8.23 released
Hi, I'm glad to announce the immediate availability of mc-4.8.23! This is a maintenance release including several improvements and fixes for issues found since the last one, most notably we hope that long standing gpm problems are finally taken care of. In as far as improvements are concerned, the deletion of large directory structures should now take significantly less time. In other news, "File exists" dialog layout has been improved, and there is now a possibility to redefine key bindings for the top menu. For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.23 As usual, kudos to Andrew Borodin, whose tireless work made this release possible, as well as all of our contributors, including translators. -- 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
Re: Help testing release candidate / mc-4.8.23-rc1
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! > > 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 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. ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing release candidate / mc-4.8.23-rc1
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.22 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.22-166-gcd16697a3.tar.xz $ sha256sum mc-4.8.22-166-gcd16697a3.tar.xz c518e0c746fd6755dd0733e70356c8e6a37bda4122c222de961ab78db24780fa mc-4.8.22-166-gcd16697a3.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 30 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
Fwd: [RFC] mceditor: add .editorconfig support
Sent from my iPad Begin forwarded message: > From: "Vladislav Grishenko" > Date: 13. March 2019 at 13:55:22 CET > To: , > Subject: [RFC] mceditor: add .editorconfig support > > Hello, > > There’s old ticket https://midnight-commander.org/ticket/3367 for > https://editorconfig.org/ support. > With spreading of editorconfig support (vs, plugins for clion, notepad++, and > so on, just see the list on the site) and different-styled sourced > (c/c++/py/js/yaml/etc) it becomes quite common and useful. > Unlike https://midnight-commander.org/attachment/ticket/3068/ (Vim's modeline > support), editorconfig needs no file data, just file path which is obviously > instantly available. > > I’ve made quick initial support as PoC, please refer > https://github.com/themiron/mc/commit/2d63096c16d868e0e0fe6cfa7ca5fcebe25c0a99 > May I ask you for some guidelines / suggestions / comments for further better > integration required before it possibly can appear in mc upstream (as my main > goal)? > > p.s tried to reach via old mc-dev@ jabber conf, but seems there’s nobody left > since last time I were chatting in it with you. > > Best Regards, Vladislav Grishenko > ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.22 released
Hi, I'm glad to announce the immediate availability of mc-4.8.22! This is a maintenance release mainly including fixes for issues found since the last one, most notably several crashers, an annoying problem with quiet file overwriting, correct preservation of sftp file timestamps, as well as support for building on IBM PASE for i and latest macOS versions. Everybody is recommended to upgrade to immediately benefit from these improvements! For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.22 As usual, kudos to Andrew Borodin, whose work made this release possible, as well as all of our contributors, including translators. Happy New Year 2019! -- 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
Help testing release candidate / mc-4.8.22-rc1
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.21 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.21-108-g4b46e6194.tar.xz $ sha256sum mc-4.8.21-108-g4b46e6194.tar.xz 95eb67435d0ab7ab08753c6057250b2a791468218c0ad5758e8b6bd2df3630d2 mc-4.8.21-108-g4b46e6194.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 29 VM which I'm also going to use to build the final release early next year 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
Re: crash when returning to panels by pressing Ctrl-O
Better still would be to create a linked issue in the upstream tracker, because problems reported on the list tend to get lost... On Sun, 14 Oct 2018, Nerijus Baliunas via mc-devel wrote: Hello, I posted https://bugzilla.redhat.com/show_bug.cgi?id=1639016 but duplicate it here too. I get lots of crashes when returning to mc panels from terminal by pressing Ctrl-O. # coredumpctl debug PID: 10643 (mc) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Sun 2018-10-14 12:54:41 EEST (10min ago) Command Line: /usr/bin/mc -P /var/tmp/mc-root/mc.pwd.10566 Executable: /usr/bin/mc ... Core was generated by `/usr/bin/mc -P /var/tmp/mc-root/mc.pwd.10566'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x55e1c86ac045 in display_mini_info (panel=0x55e1ca8856f0) at panel.c:1006 1006if (S_ISLNK (panel->dir.list[panel->selected].st.st_mode)) Missing separate debuginfos, use: dnf debuginfo-install glib2-2.58.1-1.fc29.x86_64 glibc-2.28-9.fc29.x86_64 gpm-libs-1.20.7-16.fc29.x86_64 libssh2-1.8.0-8.fc29.x86_64 openssl-libs-1.1.1-3.fc29.x86_64 pcre-8.42-4.fc29.x86_64 zlib-1.2.11-14.fc29.x86_64 (gdb) bt #0 0x55e1c86ac045 in display_mini_info (panel=0x55e1ca8856f0) at panel.c:1006 #1 0x55e1c86b0fdb in panel_callback (w=0x55e1ca8856f0, sender=, msg=, parm=, data=) at panel.c:3673 #2 0x55e1c86a4404 in setup_panels () at layout.c:756 #3 0x55e1c86a8e2d in midnight_callback (w=, sender=, msg=, parm=0, data=) at midnight.c:1470 #4 0x55e1c868f4c2 in send_message (data=0x0, parm=0, msg=MSG_RESIZE, sender=0x0, w=) at ../../lib/widget/widget-common.h:210 #5 dialog_switch_resize (d=) at dialog-switch.c:120 #6 dialog_change_screen_size () at dialog-switch.c:374 #7 0x55e1c868f51d in mc_refresh () at dialog-switch.c:349 #8 0x55e1c8710faf in dir_list_reload (list=list@entry=0x55e1ca885738, vpath=0x55e1ca892e50, sort=0x55e1c870fc30 , sort_op=sort_op@entry=0x55e1ca8857a8, fltr=0x0) at dir.c:800 #9 0x55e1c86ae366 in panel_reload (panel=panel@entry=0x55e1ca8856f0) at panel.c:4424 #10 0x55e1c86ae578 in update_one_panel_widget (panel=0x55e1ca8856f0, flags=, current_file=0x55e1ca979d10 "libicui18n.so.62.1") at panel.c:4028 #11 0x55e1c86aeb69 in update_one_panel ( current_file=0x , flags=UP_OPTIMIZE, which=0) at panel.c:4049 #12 update_panels (flags=flags@entry=UP_OPTIMIZE, current_file=current_file@entry=0x ) at panel.c:4819 #13 0x55e1c86866de in toggle_panels () at execute.c:554 #14 0x55e1c870e73d in view_other_cmd () at cmd.c:1216 #15 0x55e1c86a8975 in midnight_execute_cmd (sender=0x0, command=45) at midnight.c:1330 #16 0x55e1c86a8f72 in midnight_callback (w=, sender=, msg=, parm=16399, data=) at midnight.c:1565 #17 0x55e1c86906e1 in send_message (data=0x0, parm=16399, msg=MSG_UNHANDLED_KEY, sender=0x0, w=0x55e1ca864800) at ../../lib/widget/widget-common.h:210 #18 dlg_key_event (d_key=16399, h=0x55e1ca864800) at dialog.c:489 #19 dlg_process_event (h=0x55e1ca864800, key=16399, event=) at dialog.c:1168 #20 0x55e1c8690c61 in frontend_dlg_run (h=0x55e1ca864800) at dialog.c:541 #21 dlg_run (h=0x55e1ca864800) at dialog.c:1199 #22 0x55e1c86a9e2c in do_nc () at midnight.c:1791 #23 0x55e1c868474b in main (argc=, argv=) at main.c:409 Regards, Nerijus ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: change default configuration
I fought against it for quite some time, but, in the end, this was not a fight
that I could win. Debian Policy says it should be this way, thus so it is, and
so it will be :-/
Sent from my iPad
> On 27. Jul 2018, at 21:06, Felix Miata via mc-devel
> wrote:
>
> Egmont Koblinger composed on 2018-07-27 20:43 (UTC+0200):
>
>> Oswald Buddenhagen wrote:
>
>>> fwiw, i always found that default setting rather surprising and
>>> counter-productive, too. the vim/emacs/etc. hardliners will find the way
>>> to launch their personal deity, err, preferred editor soon enough, while
>>> average joe (in as far as he uses mc at all) won't appreciate being
>>> dropped into vi by default ("how do i quit that crap?!" was also my
>>> first experience).
>
> +++
>
>> I fully agree, and recommend to change the default to mcedit.
>
> AFAICT, external is a misfeature of .deb mc packages, one of the most annoying
> things about using Knoppix (pause after run off in mc being the other). Fedora
> and openSUSE rpms AFAICR are always mcedit.
> --
> "Wisdom is supreme; therefore get wisdom. Whatever else you
> get, get wisdom." Proverbs 4:7 (New Living Translation)
>
> Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata *** http://fm.no-ip.com/
> ___
> mc-devel mailing list
> https://mail.gnome.org/mailman/listinfo/mc-devel
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.21 released
Hi, I'm glad to announce the immediate availability of mc-4.8.21! This is a maintenance release mainly including fixes for issues found since the last one, most notably the nasty -31 error that was plaguing SFTP protocol support for a long time. Everybody is recommended to upgrade to immediately benefit from these improvements! For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.21 I highly appreciate the work of Andrew Borodin, who made this release possible, as well as all of our contributors, including translators. As always, we hope to accept more patches for the next version, with many waiting for reviews and tests, of which we sadly have way too few, but our resources are constrained as ever, so bear with us. Anyways, summertime is finally there, so enjoy all it brings along :-) ! -- 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
Help testing release candidate / mc-4.8.21-rc1
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.20 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.20-144-ge20376f.tar.xz $ sha256sum mc-4.8.20-144-ge20376f.tar.xz e8a4ed465006bd761181938ad5c5a4da24e01fbaa68877b4754cbbdd91b5a2a0 mc-4.8.20-144-ge20376f.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 25 VM which I'm also going to use to build the final release. I'd particularly appreciate feedback regarding builds on platforms that we aren't regularly using ourselves (non-Linux), like FreeBSD, Solaris, etc. If no serious regressions are going to be uncovered, we'll probably release 4.8.21 in the week to come... Many thanks! P.S. Known build problem on macOS 10.13 High Sierra can be currently worked around by forcing utimensat support to off during the build: $ export ac_cv_func_utimensat=no -- 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
Midnight Commander 4.8.20 released
Hi, I'm glad to announce the immediate availability of mc-4.8.20! This is a maintenance release including mainly fixes for issues found since the last one, most notably a bug in the nsec timestamps support code which caused loss of timestamps under some circumstances. Everybody is recommended to upgrade to immediately benefit from these improvements! For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.20 I highly appreciate the work of Andrew Borodin, who made this release possible, as well as our regular contributor Mooffie and others, including our translators. As always, we hope to accept more patches for the next version, with many waiting for reviews and tests, of which we sadly have way too few, but our resources are constrained as ever, so bear with us. It's a bit too early to wish everybody a Merry Christmas & a Happy New Year, but since no release is forthcoming in December anyways, I'll still use the opportunity to do so :-) -- 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
Re: Help testing release candidate / mc-4.8.20-rc1
Sorry, overzealous SELinux... :-/ should work now! On Sat, 18 Nov 2017, Egmont Koblinger wrote: Hi, 403 Forbidden. cheers, e. On Sat, Nov 18, 2017 at 7:59 PM, Yury V. Zaytsev <y...@shurup.com> 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.19 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.19-128-g92f190e.tar.xz $ sha256sum mc-4.8.19-128-g92f190e.tar.xz d4106d955c586cf593a0558c9c27d51d09dfcca7ea6386873b0922cd5d05add6 mc-4.8.19-128-g92f190e.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 25 VM which I'm also going to use to build the final release. I'd particularly appreciate feedback regarding builds on platforms that we aren't regularly using ourselves (non-Linux), like FreeBSD, Solaris, etc. If no serious regressions are going to be uncovered, we'll probably release 4.8.20 in the week to come... Many thanks! P.S. Known build problem on macOS 10.13 High Sierra can be currently worked around by forcing utimensat support to off during the build: $ export ac_cv_func_utimensat=no -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing release candidate / mc-4.8.20-rc1
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.19 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.19-128-g92f190e.tar.xz $ sha256sum mc-4.8.19-128-g92f190e.tar.xz d4106d955c586cf593a0558c9c27d51d09dfcca7ea6386873b0922cd5d05add6 mc-4.8.19-128-g92f190e.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 25 VM which I'm also going to use to build the final release. I'd particularly appreciate feedback regarding builds on platforms that we aren't regularly using ourselves (non-Linux), like FreeBSD, Solaris, etc. If no serious regressions are going to be uncovered, we'll probably release 4.8.20 in the week to come... Many thanks! P.S. Known build problem on macOS 10.13 High Sierra can be currently worked around by forcing utimensat support to off during the build: $ export ac_cv_func_utimensat=no -- 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
Re: mc macro recording/editing issues
On Tue, 19 Sep 2017, Sergey Naumov wrote: Also is there a way for macros to get cursor position in a file in a form of offset from the beginning of the file? What I'm trying to achieve is to get some sort of autocompletion for golang using gocode, and it is done like this: I think you might get luckier with mcedit/etags integration, not sure if there it anything etags-like for go, but if I were you, I'd rather look into this... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: new MC logo proposal
On Fri, 14 Jul 2017, pierre-philipp braun wrote: Once you've picked one up, myself or one of yours can easily generate resized flavors and favicon.ico accordingly. Yes, there was no budget for this. But I find some of those pngs pretty neat esp. `mc-bigchief.png`. I think the `mc-digital.png` is a rather funny pun on the double panel manager idea and a clever design for a text logo, but I can't see how we can possibly make use of it... it's certainly all but appropriate for replacing the current logo, favicons and stuff. Also, FYI: http://midnight-commander.org/ticket/2314 -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: hard links vs symlinks
On Wed, 5 Jul 2017, Piscium wrote: The hard link command (C-x l) behaves differently, it does not pre-fill any name. I suppose that the only way to have the hard link command pre-fill the name similar to the the behaviour for the symlink would require a code change? Or is there a configuration option somewhere for it? Yes, it would require a code change. You can make a patch by looking at the code for the other command, and post it to the Trac for everybody. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] Initialize struct stat st_[acm]tim.tv_nsec when present
On Sat, 6 May 2017, Nerijus Baliunas wrote: It works, and it fixes my yesterday reported problem with zip/rar subdirs. Thanks! IMHO it would be nice to release 4.8.20 with this fix, it is important. Thanks for the confirmation, I have put the branch on review. Regarding the release, I'm not sure about it. As far as I understand, it's not a regression, but a bug that has been present for a very long time, so if this is true, then we are not really in a hurry. But if Andrew would say we do have to release the next version once this fix is in, I will try to find time to start this process... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] Initialize struct stat st_[acm]tim.tv_nsec when present
I've created a ticket and branch for this patch: https://midnight-commander.org/ticket/3821#comment:1 I've also patched all other places where stat is filled manually that I could find. The all builds & tests seem to run through. Does this version work, or problems remain? On Wed, 19 Apr 2017, Andrey Gursky wrote: struct stat in libc for Linux kernel contains few fields more since 14+ years [1]. from bits/stat.h: struct timespec st_atim;/* Time of last access. */ struct timespec st_mtim;/* Time of last modification. */ struct timespec st_ctim;/* Time of last status change. */ # define st_atime st_atim.tv_sec/* Backward compatibility. */ # define st_mtime st_mtim.tv_sec # define st_ctime st_ctim.tv_sec The conventional fields became an alias. POSIX.1-2008 made struct stat st_[acm]tim mandatory [2]. OS takes care to initialize struct stat properly [3]. By not using an OS syscall or a libc wrapper to fill struct stat, we have to take care of initializing all fields (or at least those being used later) explicitly. [1] https://www.sourceware.org/ml/libc-alpha/2002-12/msg00011.html [2] https://www.sourceware.org/ml/libc-alpha/2009-11/msg00102.html [3] https://www.sourceware.org/ml/libc-alpha/2002-12/msg00013.html Fixes: file timestamps not preserved (https://mail.gnome.org/archives/mc-devel/2017-April/msg0.html) Reported-By: Nerijus Baliunas <neri...@users.sourceforge.net> --- configure.ac| 2 +- src/vfs/cpio/cpio.c | 15 +++ src/vfs/tar/tar.c | 3 +++ 3 files changed, 19 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 45836fcaf..387110daf 100644 --- a/configure.ac +++ b/configure.ac @@ -181,7 +181,7 @@ AC_TYPE_PID_T AC_TYPE_UID_T AC_STRUCT_ST_BLOCKS -AC_CHECK_MEMBERS([struct stat.st_blksize, struct stat.st_rdev]) +AC_CHECK_MEMBERS([struct stat.st_blksize, struct stat.st_rdev, struct stat.st_mtim]) gl_STAT_SIZE AH_TEMPLATE([sig_atomic_t], diff --git a/src/vfs/cpio/cpio.c b/src/vfs/cpio/cpio.c index dba1a07c3..ffe6267cf 100644 --- a/src/vfs/cpio/cpio.c +++ b/src/vfs/cpio/cpio.c @@ -462,9 +462,15 @@ cpio_create_entry (struct vfs_class *me, struct vfs_s_super *super, struct stat entry->ino->st.st_mode = st->st_mode; entry->ino->st.st_uid = st->st_uid; entry->ino->st.st_gid = st->st_gid; +#ifdef HAVE_STRUCT_STAT_ST_MTIM +entry->ino->st.st_atim = st->st_atim; +entry->ino->st.st_mtim = st->st_mtim; +entry->ino->st.st_ctim = st->st_ctim; +#else entry->ino->st.st_atime = st->st_atime; entry->ino->st.st_mtime = st->st_mtime; entry->ino->st.st_ctime = st->st_ctime; +#endif } g_free (name); @@ -589,6 +595,9 @@ cpio_read_bin_head (struct vfs_class *me, struct vfs_s_super *super) st.st_rdev = u.buf.c_rdev; #endif st.st_size = (u.buf.c_filesizes[0] << 16) | u.buf.c_filesizes[1]; +#ifdef HAVE_STRUCT_STAT_ST_MTIM +st.st_atim.tv_nsec = st.st_mtim.tv_nsec = st.st_ctim.tv_nsec = 0; +#endif st.st_atime = st.st_mtime = st.st_ctime = (u.buf.c_mtimes[0] << 16) | u.buf.c_mtimes[1]; return cpio_create_entry (me, super, , name); @@ -658,6 +667,9 @@ cpio_read_oldc_head (struct vfs_class *me, struct vfs_s_super *super) u.st.st_rdev = hd.c_rdev; #endif u.st.st_size = hd.c_filesize; +#ifdef HAVE_STRUCT_STAT_ST_MTIM +u.st.st_atim.tv_nsec = u.st.st_mtim.tv_nsec = u.st.st_ctim.tv_nsec = 0; +#endif u.st.st_atime = u.st.st_mtime = u.st.st_ctime = hd.c_mtime; return cpio_create_entry (me, super, , name); @@ -736,6 +748,9 @@ cpio_read_crc_head (struct vfs_class *me, struct vfs_s_super *super) u.st.st_rdev = makedev (hd.c_rdev, hd.c_rdevmin); #endif u.st.st_size = hd.c_filesize; +#ifdef HAVE_STRUCT_STAT_ST_MTIM +u.st.st_atim.tv_nsec = u.st.st_mtim.tv_nsec = u.st.st_ctim.tv_nsec = 0; +#endif u.st.st_atime = u.st.st_mtime = u.st.st_ctime = hd.c_mtime; return cpio_create_entry (me, super, , name); diff --git a/src/vfs/tar/tar.c b/src/vfs/tar/tar.c index 3afd8d68d..4b674739d 100644 --- a/src/vfs/tar/tar.c +++ b/src/vfs/tar/tar.c @@ -442,6 +442,9 @@ tar_fill_stat (struct vfs_s_super *archive, struct stat *st, union record *heade } st->st_size = h_size; +#ifdef HAVE_STRUCT_STAT_ST_MTIM +st->st_atim.tv_nsec = st->st_mtim.tv_nsec = st->st_ctim.tv_nsec = 0; +#endif st->st_mtime = tar_from_oct (1 + 12, header->header.mtime); st->st_atime = 0; st->st_ctime = 0; -- 2.12.2+git20170411 ___________ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: file timestamps not preserved
On Sat, 6 May 2017, Nerijus Baliunas wrote: On Fri, 5 May 2017 23:31:50 +0200 Andrey Gursky <andrey.gur...@e-mail.ua> wrote: I've downloaded the original mc 4.8.19 release, applied the patches, run autoreconf, then configure, make install and it works for me. Have you tested with the file you've sent me? If yes, I'm curious what could be else different?.. BTW, if I call autoconf instead of autoreconf, I cannot see anything happens. With autoreconf instead of autoconf it is OK. Thanks. You have to use ./autogen.sh to bootstrap the build system. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] Remove unused check in configure.ac
On Wed, 19 Apr 2017, Andrey Gursky wrote: AC_STRUCT_ST_BLOCKS is a leftover from cleanup in 0ba019a90b3798abae32ba261e72b737dc945615 I don't understand why you're saying that this macro is unused. It defines HAVE_STRUCT_STAT_ST_BLOCKS if struct `stat` contains an `st_blocks` member. This define is currently used in branches all over our codebase. https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Particular-Structures.html#Particular-Structures --- configure.ac | 1 - 1 file changed, 1 deletion(-) diff --git a/configure.ac b/configure.ac index 387110daf..ac81404f5 100644 --- a/configure.ac +++ b/configure.ac @@ -180,7 +180,6 @@ gl_PROMOTED_TYPE_MODE_T AC_TYPE_PID_T AC_TYPE_UID_T -AC_STRUCT_ST_BLOCKS AC_CHECK_MEMBERS([struct stat.st_blksize, struct stat.st_rdev, struct stat.st_mtim]) gl_STAT_SIZE -- 2.12.2+git20170411 ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Update translations from Transifex
On Sat, 29 Apr 2017, Antoni Bella Pérez via mc-devel wrote: I updated Catalan (ca) translations from Transifex and I ask them to update the repository. Doing so automatically or on request? Normally, we pull in translations from Transifex manually before release, but since there have been quite some changes already, I've imported them right now... Thank you for your contribution! -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.19 released
Hi, On Sun, 5 Mar 2017, Sergei Trofimovich wrote: Yay! Looks like a set of vfs shell helpers were added in here. If I remember correctly, no new helpers, but many existing helpers turned out to be broken and were fixed after the test suite was introduced. When running 'make check' I have single extfs test failure: # FAIL: 1 See tests/src/vfs/extfs/helpers-list/test-suite.log Thanks, we'll have a look. The log file is missing actual diff. I suggest adding diff output inline to ease bug reporting. Might be a good idea, I thought the diff was generated in the temporary directory, but apparently, this is not the case. And a few others. These tests look fragile. That's very curious, because the tests shouldn't be actually using the tools themselves, but they should rather be only checking whether the extfs scripts are still able to parse pre-recorded output of the tools. Therefore, I would hope that it's not version drift of the tools, but rather coreutils / awk / ... whatever the scripts depend upon to parse pre-recorded output, and as such you have identified a valid problem with parsing not being robust enough / working differently with newer coreutils / awk / etc. Or else, in your case, real output is used instead of mocked stuff, which would be truly bizarre, but would also point to a valid problem with the test suite. One thing is clear though, something's gone wrong here, could you please be so kind to create a ticket? Thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.19 released
Hi, I'm glad to announce the immediate availability of mc-4.8.19! This is a maintenance release which includes many bugfixes and several new exciting features, the most notable of which are support for True Color capable terminals (and first skins!) contributed by Egmont Koblinger and support for timestamps with nanosecond precision on Linux contributed by Andrey Gursky. For the detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.19 Traditionally, big thanks goes to our hero committer Andrew Borodin, as well as our regular contributors Mooffie, Andreas Mohr and others, including our translators. This time I have the particular pleasure to welcome Mooffie of the friendly mc^2 fork's fame as our new committer, and note how he has already delivered many valuable additions to mc for this release, including an actual test suite for the extfs helpers! As always, we hope to accept more patches for the next version, with many waiting for reviews and tests, of which we sadly have way too few, but our resources are constrained as ever, so bear with us. Having that said, we in full choir hail thy approach, O Spring! -- 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
Help testing release candidate / mc-4.8.19-rc1
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.18 release: http://www.midnight-commander.org/nopaste/tarball/mc-4.8.18-250-g60faabd.tar.xz $ sha256sum mc-4.8.18-250-g60faabd.tar.xz e88ac5a087a71ea5c63ccb44bc10eac706ebac5a19f950b1b06f1fb7adaad3c6 mc-4.8.18-250-g60faabd.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 25 VM where I'm also going to build the final release (previous release was built on Fedora 23). I'd particularly appreciate feedback regarding builds on platforms that we aren't regularly using ourselves (non-Linux), like FreeBSD, Solaris, etc. If no serious regressions are going to be uncovered, we'll probably release 4.8.19 in the week to come... 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
Re: environment var
On Wed, 28 Dec 2016, Nerijus Baliunas wrote: Why DBUS_SESSION_BUS_ADDRESS has an original value, and not the one which I exported? Apparently this variable is somehow set in your profile when it is executed (.bashrc), so when subshell spawns, it overwrites it. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Possible usability addition to mc quickview panel
On Sat, 15 Oct 2016, Sacha Hony wrote: I have inspected the mc source code and it seems like a relative simple addition because the whole framework of calling external programs based on file-magic is already there. Please use the ticket tracker to file feature requests and propose patches, whatever you write to the mailing list will eventually get lost. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: root:root ownership of ~/.local/share/mc
On Sat, 17 Sep 2016, David Martín wrote: I'm not sure if this is to be considered as a bug or if it is just an «unfortunate coincidence». In case it's of any use I will report: Well, that's your own fault, you should be rather using: sudo -i mc -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: MC bug?
On Thu, 29 Sep 2016, Павел Хмиленко wrote: MC installed with brew on macOS Sierra. Getting this error message when trying to run as superuser. https://gyazo.com/5867954c6971e643a89c5772d1982111 screenshot Runs as superuser only if sudo mc -u --nosubshell Well, it couldn't detect your root shell for one reason or another, or rather it detected it as SHELL_SH and doesn't know what to do with it. You can try the patch from this ticket and see if it works for you: http://www.midnight-commander.org/ticket/3692#comment:7 There is some work done there to make subshell detection much more robust. In the mean time, you can of course always use bash explicitly: sudo /bin/bash -c mc -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.18 released
On Sun, 9 Oct 2016, Nerijus Baliunas wrote: On Mon, 3 Oct 2016 17:18:12 +0200 (CEST) "Yury V. Zaytsev" <y...@shurup.com> wrote: Woops, copy paste mistake. I used a previous mail announcement. MC is compiled with --with-x since 4.8.17, as you already asked me :) Oh, as a matter of fact, I had a faint suspicion that we've already had this conversation... now all that is left is to somehow inflict it on the Fedora maintainers ;-) Reported - https://bugzilla.redhat.com/show_bug.cgi?id=1383054 Thank you! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit: basic syntax file for rust language
On Tue, 4 Oct 2016, Laurent Wandrebeck wrote: Please find attached a syntax file to add (basic, and probably still a bit buggy) rust support. Could you please submit a patch via Trac, so it doesn't get lost on the mailing list? Many thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.18 released
On Mon, 3 Oct 2016, Laurent Wandrebeck wrote: Woops, copy paste mistake. I used a previous mail announcement. MC is compiled with --with-x since 4.8.17, as you already asked me :) Oh, as a matter of fact, I had a faint suspicion that we've already had this conversation... now all that is left is to somehow inflict it on the Fedora maintainers ;-) -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.18 released
Hi Laurent, On Mon, 3 Oct 2016, Laurent Wandrebeck wrote: I’ve used official tar.xz package, and mc was built with the following options: --without-x \ It would be great if you could try to rebuild --with-x and libX11-devel as a build dependency (no other changes are needed). This allows mc to use X11 to detect some key modifiers if running inside graphical terminal emulators (i.e. Meta + Enter). I'm not quite sure why Fedora people have turned this off. Maybe they simply don't understand what it does and believe that this will introduce an install-time / run-time dependency on X11. That is not the case, mc will be able to install and run without X11 just as before, only in addition it will also dynamically load X11 libraries and use them if they are available. Thanks for your packages! -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.18 released
Hi, I'm glad to announce the immediate availability of mc-4.8.18! This is a maintenance release which mainly includes bugfixes and addresses several regressions reported against the previous version. For a detailed list of changes since the last release, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.18 Traditionally, big thanks goes to Andrew Borodin, who's made this release possible, as well as our regular contributors Mooffie, Andreas Mohr and others, including our translators. As always, we hope to accept more patches for the next version, but our test suite is in shambles, which makes reviews a daunting and extremely tedious task. Contributions in this area, and, in particular, unit tests for outstanding patches are especially welcome! -- 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
Re: Help testing the pre-release of mc-4.8.18
On Mon, 26 Sep 2016, Andrey Tataranovich wrote: I think that must have the same underlying reason as this ticket: http://www.midnight-commander.org/ticket/3406 ... do you have the same issue with 4.8.17, i.e. is this a regression, or an old bug? In any case, I've just tried it, and for me it works fine. I'm sorry. I have rechecked and find that cyrillic names do not lead to this issue but a broken symlink that points to currently unavailable location. Try to create broken symlink and view this directory via SFTP. Okay, so that's really the old #3406 bug... I couldn't find any ticket re. zoo listing on the Trac. Could you please make one with a reproducer? If it's not a regression, this won't be a priority, but it would be nice to fix it for the next release. I have created ticket for this issue: https://www.midnight-commander.org/ticket/3696 Thank you very much! One day, we'll get to it. Hopefully. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Help testing the pre-release of mc-4.8.18
Hi Andrey, Thank you for testing! On Mon, 26 Sep 2016, Andrey Tataranovich wrote: Have found "SFTP Protocol error (-31)" when entering directory with cyrillic names in it. But after error MC show correct directory listing. I think that must have the same underlying reason as this ticket: http://www.midnight-commander.org/ticket/3406 ... do you have the same issue with 4.8.17, i.e. is this a regression, or an old bug? In any case, I've just tried it, and for me it works fine. Checked multiple archive formats and noticed that zoo archive listing is broken (was already broken in 4.8.17). I couldn't find any ticket re. zoo listing on the Trac. Could you please make one with a reproducer? If it's not a regression, this won't be a priority, but it would be nice to fix it for the next release. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Help testing the pre-release of mc-4.8.18
Hi there, TLDR; we would appreciate if you could test the following tarball on your systems and report any blocker regressions as compared to 4.8.17: http://www.midnight-commander.org/nopaste/tarball/mc-4.8.17-122-g6822251.tar.xz $ sha256sum mc-4.8.17-122-g6822251.tar.xz e9a4a418d9d551b4a58fffa907c001a5eb84d2fe2e490d221f99c1d1642fecbd A longer explanation: we're thinking of making another bugfix release next week or so to push out the changes accumulated in master so far. However, I find it very unsatisfying that we've been getting an influx of reports concerning some really annoying regressions right after the releases in the past, so, this time around, I propose that distro maintainers and regular users check the pre-release tarball beforehand and report FTBFSs & regressions if any, such that this time (hopefully) we'll break out of this vicious cycle. I've built this tarball out of the latest master with translations from Transifex pulled in on the same VM where I build regular releases. Many thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc : bug in locale fr
Bonsoir Michel, On Mon, 29 Aug 2016, mab974 wrote: It should be great to change " trié" to "N Trié" for example "o" is free. For now, i change it manually but it's worth saying it... I've just fixed it on Transifex, thank you for the report! -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc^2 news (august 2016)
On Sun, 11 Sep 2016, Andrey Gursky wrote: Once I read the beginning of this last sentence I knew I've heard something very similar already before. [...] ... and so, what is that more exactly that you are trying to tell me? I can't see how your email brings anything new to the table. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc^2 news (august 2016)
On Fri, 19 Aug 2016, denisgolovan wrote: It looks to me it will require becoming an MC developer first. To make a positive influence on this process, I mean. Estimating/tearing tickets apart/etc. requires quite a lot of project internal structure knowledge. That's correct; it's a very time-intensive and demanding work... In my personal view of the situation, however, then the biggest problem with mc codebase today is the abysmal state of test coverage, which makes maintenance a gamble and demands extreme efforts to review patches. Before this problem is addressed, I'm not very positive about soliciting massive contributions, which will end up rotting on the Trac waiting for code reviews and rewrites... that might never come. Hm. That doesn't seem too optimistic... No, it doesn't sound optimistic at all, but I don't think that covering up problems is going to be of any help here. As they say, recognizing the issues is the first step toward getting them addressed. Midnight Commander is a complex piece of software, maybe not so much due to the inherent complexity of the tasks which it is designed to deal with, but due to subtle variations of platforms, compilers, libraries, terminals, operating systems, etc. Now, if this whole complexity is not covered with a reasonable amount of tests, at some point, there is no chance in hell you are not going to introduce obscure side-effects by most innocently looking changes. This, in turn, entails that overly high cognitive load is required to make halfway meaningful patch reviews, which end up taking ages, and one still ends up overlooking stuff, and introducing new bugs by applying a bug fix. To my mind, this is the biggest technical and organizational problem we are facing right now; I hope that I can do something about that when I have more time for mc. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc^2 news (august 2016)
On Thu, 18 Aug 2016, denisgolovan wrote:
But why not try some form of crowd-funding / bounty-hunting?
I can only speak for myself and my experience is that with most successful
crowd-funding projects, maintainers end up getting paid several times
lower wages than the market rates, and this income is unstable (that is,
no indications whatsoever as to what happens when the money from the
campaign runs out). In exchange for that, however, they get to work on an
exciting open source project of their own choosing and enjoy flexible
working times.
I have a lot of respect for the engineers who do go for this (I know some,
and they are really seriously brilliant), but, very unfortunately, this is
not a compromise that I'm personally prepared to accept.
Besides, I don't even want to work on mc all day long :-) It's a great
hobby project for a few days per week, but that's about it. So, my
personal dream would be to find an employer who is ready to sponsor 1/2
days per week of open source work (the more, the better ;-) ), such that I
could put part of this time towards mc, but on a regular basis (i.e.
weekly) rather than ad hoc, and still enjoy all the perks of not being
"self-employed"; how this pans out we shall see in the near future.
Now, yet again, this is just my personal view of things...
I mean to structure those 500+ bugs/features ("future" milestone) in
some meaningful way + put some estimates(weeks, dollars)/difficulty for
them and try to pursue people on popular Linux forums for support.
If you are willing to invest some serious effort into pulling out
something like that, let me know if there is anything I could reasonably
help you with.
In my personal view of the situation, however, then the biggest problem
with mc codebase today is the abysmal state of test coverage, which makes
maintenance a gamble and demands extreme efforts to review patches.
Before this problem is addressed, I'm not very positive about soliciting
massive contributions, which will end up rotting on the Trac waiting for
code reviews and rewrites... that might never come.
--
Sincerely yours,
Yury V. Zaytsev
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc^2 news (august 2016)
On Wed, 17 Aug 2016, Mooffie wrote: * "Folder Jumping" A feature borrowed from GitHub.com.[1] Sounds awesome! * Unwind Automatically convert Windows/DOS line-ends to Unix, in the editor. This is something that has often been requested before under many guises (mainly line endings autodetection), however, I'm not sure whether automatic dos2unix conversion is the best way to handle it. I think it would be nice to have an IDEA-like behaviour where the line endings scheme is detected automatically and then the buffer is edited according to the detected scheme, however, one optionally can force automatic conversion to the desired scheme as well. // I'd like to use this opportunity to post an update re. what's going on at my end: basically, I've been inactive in the last couple of months (travelling, $dayjob), but I hope that my efforts in trying to find an employer who would be ready to sponsor some work on mc at least on the scale of several hours per week have now finally borne fruit and if all goes well I will again get more actively involved in mc this fall. In the mean time, kudos to Andrew who is single-handedly doing some excellent work on mc right now... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.17 released
On Mon, 9 May 2016, Laurent Wandrebeck wrote: I’ll mail Jindrich in a couple minutes (you’ll be cc’ed). Hi Laurent, Your help is much appreciated! If you don't get a reply soon, I think it would be better to create an issue in the Fedora tracker with a patch attached, so that it is not forgotten; I know that he's also very busy now at his new $dayjob... -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.17 released
On Mon, 9 May 2016, Laurent Wandrebeck wrote: Done, builds on their way. Just make sure that it doesn't pull x11 in the Requires, which shouldn't happen, but better check it still. I can send him my updates if you want. I certainly wouldn't mind that :-) I'm trying to keep an eye on downstreams (Debian, Red Hat, Gentoo, Arch), but I only have so much time available for the purpose... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.17 released
On Mon, 9 May 2016, Laurent Wandrebeck wrote: I can get rid of --without-x if you want. To provide best experience for the users, you should add the equivalent of libx11-dev to BuildRequires and build --with-x. I just checked Fedora 24 package, it still uses --without-x and -- enable-vfs-mcfs Well, I forgot to let Jindrich know last time I saw him :-( and I didn't manage to send a patch his way so far, but this is wrong. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.17 released
Hi Laurent, Many thanks! On Mon, 9 May 2016, Laurent Wandrebeck wrote: I’ve used official tar.xz package, and mc was built with the following options: --with-screen=slang \ --enable-charset \ --without-x \ Why without X? It's only needed in BuildDeps, if installed on a system w/o X it will still work, because X stuff is dlopen'ed only when available. -- Sincerely yours, Yury V. Zaytsev___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.17 released
Hi, I'm glad to announce the availability of mc-4.8.17! This is a maintenance release that includes bugfixes for a bunch of very annoying bugs that surfaced in the previous version (FISH, patchfs, segfault and tcsh detection on FreeBSD) and brings several new features. Copy & move operations now use an adaptive buffer, just like the corresponding coreutils commands, which will significantly improve the performance (hopefully!) for many of our users. Move to the new high-level mouse API has not only simplified our code, but also resolved a number of long-standing mouse bugs. Finally, the new panel centered scrolling mode is weird, but fun; try it out! For a detailed list of changes since the last version, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.17 As usual, I would like to thank tireless Andrew Borodin, and our contributors Andreas Mohr, Mooffie and many others for making this release possible. We still have an enormous backlog of tickets and patches, but we are working on it as time permits, one patch at a time. Have a great summer break everyone! -- 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
Re: small request
On Thu, 28 Apr 2016, Egmont Koblinger wrote: How about, for the time being, you enable auto-save and create a simple wrapper script for yourself that replaces your mc configs (restores everything except for other_dir) before starting up mc? In my opinion, this is really where mc^2 shines. If and when we'll be able to merge it in, it will finally make it possible to get rid of so many crap micro-options that we've been dragging along for such a long time... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: small request
On Tue, 26 Apr 2016, solarflow99 wrote:
yes, exactly. thanks for the understanding, this would allow existing
behaviour to continue the way it has been for years like you mentioned,
I agree with that as well.
So, if one doesn't want other_dir to be saved automatically (like me), how
do you propose to achieve this if the current behavior is modified such
that it is excluded from panel autosave option? Introduce yet another
micro-option specifically for other_dir?
Right now, it's quite straightforward: you either get all or nothing. You
like the state being carried over? Enable autosave, which is available as
an option, but not on by default. You don't want this? Keep it off.
You propose to decouple this for some chosen option, that is other_dir,
and then we'll surely get someone complaining that he wants to be able to
turn it off, so now we'll have to introduce yet another option ("carry
over other_dir" and "carry over all other state").
How about just enabling autosave and letting it be? Or else, try mc^2 ;-)
--
Sincerely yours,
Yury V. Zaytsev
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.16 released
On Tue, 2016-03-15 at 09:31 +0100, wwp wrote: > > I notice that when configuring with slang, the configure summary > doesn't mention it, whereas for ncurses it explicitely mentions it. > See for instance (w/ --with-screen=slang or no --with-screen, same > output here): Yes, I've noticed this as well, it's a bug in our ncurses/slang detection macro, but it's purely cosmetic. I didn't manage to create a ticket for this so far, but if you can do it, it will be appreciated and maybe one day we'll even get to it. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Annoying bug in FISH, could you please patch your packages?
Hi folks, It would be very kind of you, if you could include the following patch in your mc-4.8.16 packages before the shit really hits the fan: http://www.midnight-commander.org/ticket/3611 Unfortunately, while trying to fix another bug in FISH (#3599), a new bug has been introduced (#3611) as we've failed to check whether the Perl version of the ls helper is still working correctly after accepting the new changes to it :-/ Many thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.16 released
On Sun, 13 Mar 2016, solarflow99 wrote: You actually got it to build, it was complaining for me glibc had to be newer than 2.26, and nothing has that yet. thx for the package builds. You must be talking about glib2 and not glibc, yet "nothing has that yet" is still quite puzzling. Even RHEL6/7 come with newer versions, and among distributions that are still supported, only RHEL5 has an older one. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.16 released
Hi Laurent, Thanks for updating the packages! --enable-vfs-mcfs As it was already mentioned the last time, this option has been removed a long time ago. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.16 released
Hi, I'm delighted to announce the availability of the new mc-4.8.16! This is a maintenance release that includes a large number of bugfixes and a few minor new features. Amongst the most user-visible changes, we have improved on the usability (hopefully!) of the "Find File" dialog: the unsymmetrical "Search for content" checkbox is now gone; instead, leave the field empty and notice how related checkboxes will be automatically deactivated. To remind you, Ctrl+w clears the editboxes and Meta+h triggers the history drop-down, these are very handy shortcuts to make the most out of the new dialog. For a detailed list of changes since the last version, please refer to the release notes. Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.16 This release was made possible thanks to the heroic work of Andrew Borodin, a steady stream of fixes by Andreas Mohr, and contributions from Mooffie of our friendly Lua-enabled fork fame (check it out!). Finally, I would like to thank everybody who has contributed to this release, including our dedicated translators, and to remind you that we are still very much underpowered to carefully review and integrate patches in a timely manner, process bug reports and generally improve on our code base. Enjoy! -- 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
Re: mc^2 news (january 2016)
On Sun, 6 Mar 2016, Andrey Gursky wrote: Since 2+ months my patch hasn't got an owner. Does it mean the only owner it could get is you, Yury? Hmmm, let me have a look at the facts... 1) There are two committers that are currently more alive than dead. 2) I'm one of the two. 3) There was no reaction to the patch in several months by anyone other than me. Congratulations, Sherlock, you've nailed it! It seems that I'm currently the only one who cares enough to keep a tab on this particular patch. And just to commit and let people using mc from git run with a patch (and test it in background) is not a way to go by mc? Are alpha, beta, rc,... not for this? If you are asking for my personal opinion, then the answer is that the patch doesn't look too bad, but I am not comfortable with pushing this into a minor bugfix release without at least some minimal testing & having another look at what it does. Given the acumen that you've demonstrated, however, you could have as well guessed it by now. Since there were no further comments (reviews, reports that anyone has tested it on Linux / mc is still working fine on BSD, nothing!) on this bug, neither from users, nor from the developers, it seems that it's not *that* urgent after all. Nevertheless, as I said, I think that it would be generally a good thing to commit it, and I had the misfortune to indicate, that I want to try to find some time to do it for 4.8.17, but I can't tell when I will manage. Yeah, too bad for mc users. And if they are not aware of such problems, (and mc developers don't consider them as important) it doesn't save users from a fault. Once they discover them, it could be too late (e.g., all timestamps would be already truncated). Why am I disappointed? We all do it as hobby. Fixing something can be treated as my wish to invest time. Clear. But cleanup of such a fix: using upstream code style, commenting, error handling, autotools checks,.. is not such important for me, but especially for upstream. I had to spent additional time to do it, thus expecting that in such case the upstream will take time to take care of the patch. Is it not fair? (Especially in light of many other commits during all that time the patch has been submitted?) OK, this was a dramatical part. But there is also a technical consideration. For a patch submitting one is required to rebase it against current (at the time of submission) master. Thus it is important to handle patches timely. Or at least one should not accept patches submitted later that touch the same code. However this is problematic, since other people could be unaware that there is somewhere a patch and have based their code also on the visible master. Then some submitter must be asked to rebase his/her patch. But on the hobby basis it seems to me not the way to go. Though, if mc developers would do this in such cases, it would be, of course, OK for submitters. What is the mc policy about that? I'd say, that git and trac are just not enough. There must be some mechanism to make code from all submitted patches visible at one place. However it is still not clear what code one should base against when writing a new patch. So now that you've imparted to the world how heartbroken and demotivated you are because of the unfair treatment that you had to endure for your submission, what kind of reaction are you actually expecting from me? Maybe I should take the drama queen stage too and declare that I'm sick and tired of reading all this stuff, as no matter what you do, you'll never ever get any compassion or even at least some sort of respectful treatment as a committer on this list? People mostly just keep whining how their favorite patch didn't get committed yet, and tell you how you should be better spending your time. Oh well... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc^2 news (january 2016)
On Sat, 27 Feb 2016, Andrey Gursky wrote: Yury, do you plan to close all tickets with milestone 4.8.16 for the release? I can't tell; if I get time, then yes, I hope to, if not, then I'll just move them to the next one. My point was that some things actually got done, and it doesn't make sense to delay them forever, so March sounds like a good target for the next release. I'm planning to submit a new patch, but because I had no substantial feedback about my already submitted patches (2+ months) I'm feeling discouraged and postponed a cleanup. Too bad. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc^2 news (january 2016)
Hi, Too bad I'm only answering now... On Tue, 2016-01-12 at 07:40 +0200, Mooffie wrote: > > * The git commit history was rewritten. It now consists of around 90 > commits that go from genesis to today. Awesome!!!11 That'd make reviewing it a lot easier. > * New users can get an impression of mc^2 instantly: just run it and > a dialog will pop up asking you if you want to enable some "factory > defaults" goodies. Very cool, is the tip now rebased against 4.8.15? Now that there is a friendly first start screen, maybe I should give it a try on my work laptop. The screenshots look really mindblowing, in particular, the spellchecker. I always wanted to have something like this in mcedit! Just wondering, do you have any kind of internal roadmap of where you want to go now? Any ideas on how you'd like to get it merged? ~90 smaller commits is definitively better than few huge commits, but that's still quite a lot. I haven't looked at the commits themselves yet, but do you think you can try to push them in batches making the patchset against vanilla smaller and smaller, until we just go ahead and merge the remaining stuff? On a related note, I think we (or, rather, I) should start thinking about releasing 4.8.16 sometime soon. There is quite a bit of good stuff accumulated in master already. The biggest problem now is that the cleanup branch again has became quite huge. But I can always tell to myself that I trust Andrew's good judgment :-) Andrew, what do you think of this? Do you have any personal plans as to what do you want to get done before 4.8.16? -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Browsing the source
On Sun, 2016-02-21 at 19:19 +0200, Mooffie wrote: > > - GLOBAL ignores dot-files and dot-directories, so you can install it > in ".global" instead of "CVS". > > - Right now the header on the front page (index.html) is "mc". We can > change it by running htags thus: Thanks, good catches! > (BTW, it's possible to tell htags to make the front page (index.html) > show all the files in a collapsible JavaScript tree (by adding the > option `--tree-view=filetree`). But this makes the front page 96K > instead of just 13K and the browser will also download an uncompressed > jquery.js (161K) so I don't know if we should enable this feature.) I don't have a strong opinion on this to be honest... let's say I'm something like -0 on enabling this. > > If that looks fine to you, maybe we should put it somewhere on the > Trac, > > Put what on Trac? A link to http://source.mc.org? Sure. > > We also need to add to the front page of http://source.mc.org a short > introductory text pointing to the main site (and to the instructions > for producing the HTML on one's own computer). Leave it to me: I'll > investigate this and provide a patch in a couple of days. Ok, great! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc misdetects 256 color support on rxvt
On Fri, 19 Feb 2016, David Niklas wrote: I want to use a 256 color theme in rxvt but every time I select it via -S I get, a red screen telling me that my terminal does not support 256 colors. I know for a fact that rxvt does support 256 colors. So, how do you know it for a fact? Does 256colors2.pl work right? What's your $TERM, do you have terminfo set up correctly? -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Browsing the source
On Tue, 16 Feb 2016, Mooffie wrote: Ouch! I created a MarkDown instructions page before I got your reply. Here it is: https://gist.github.com/mooffie/72d58969eceb885febf5 (I'll convert it to MC's wiki sometime.) I'm trying to get this all to work with Travis & GitHub Pages and I wonder whether you would mind giving `htagsfix` a more permanent home? I'm not entirely happy with hardcoding a path to a random gist from where this script can be downloaded into the deployment script. Of course, we could include it in our repository, but I don't think that's a good idea since it's definitively not mc-specific. Maybe you could "officially" release and maintain it in a GitHub repository under your account, which sounds a bit more permanent than a gist or even try to get it pushed into GNU Global itself? -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Browsing the source
On Tue, 16 Feb 2016, Yury V. Zaytsev wrote: I can put it on http://midnight-commander.org/global or whatever would be the most appropriate URL if you can explain how to generate it. Could you please tell how much time is required for generation, I'm wondering whether I can simply have it run upon every commit or rather it would be more appropriate to let it run hourly / nightly or so. Current plan: write a shell script & commit to the repository. Set up a cron job on m-c.o to fetch, hard reset to each remote branch, and generate an index. Set up nginx to serve the directory. Alternative possibility: generate indices on Travis for every commit it builds, deploy to Github pages? Advantages: one service less on the project infra. Problem 1: Travis only has global 5.7.1, is there an Ubuntu PPA with a newer version? Problem 2: need to be smart about branches, more complicated script, looks like it will take more time to get to work. Global doesn't seem to be available as a package on RHEL though?! :-( http://www.geocities.co.jp/keep_creating/sanaly/index.html Re. wiki editing privileges, I can grant them as soon as I get access to my admin account. Done. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] Manpage fixes
On Thu, 2016-02-11 at 05:12 +0100, Denys Vlasenko wrote: > > Here it is. Hi Denys, Thanks, applied! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Trying to debug: text entry fields not acceptin 'j' or 'd' character
On Tue, 9 Feb 2016, Russell Urquhart wrote: So now we come to my question, what lib, etc., in mc would be responsible for handling text entry. Is that gettext? i DO know that for the mac mini, i am using an earlier version of gettext (0.19.4) and an earlier version of pkg-config (0.28). I still need to see what variances for the other pieces on the mac mini, but i just wanted to see if anyone could shed some light on this? Gettext is an i18n library and thus unlikely to be the cause of the problem. I would first look at SLang if I were you, it's a screen library and might indeed have something to do with your issue. Are the versions of Mac OS X and system libraries identical on both machines? If not, this adds yet another degree of freedom... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Anyone coming to FOSDEM 2016?
On Sun, 2016-01-10 at 23:18 +0100, Ben Woods wrote: > > > Yes, I will be there... mostly following the BSD track on Sunday > (since recently, I maintain the MC port for FreeBSD). Excellent, so if you are one of those, who would like to beat me up for not doing enough for mc, you're in luck! Feel free to drop me a private message if you want to meet and/or discuss anything that has to do with mc :-) -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Anyone coming to FOSDEM 2016?
Hi, If everything works out nicely, I might actually get there this year; anyone else? -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc and me
On Fri, 2015-11-06 at 19:43 +0100, Egmont Koblinger wrote: > For minor changes, such as a followup bugfix in the viewer (e.g. 3531) > I wouldn't want to wait for more than a couple of days; let's say a > week at most. Does this sound okay? A week would be fine with me for minor changes, and I trust your judgment on what's minor enough... sadly, I can't keep track of changes on this timescale, but hopefully Andrew will keep an eye and yell if something goes very very wrong. You probably already know this, but there is a helpful report page on Trac which among other things can show tickets waiting for a review... you can use that to check for tickets that need feedback. As far as I can see, you've accepted the GitHub invitation, so you should have access to the repository by now, and you've got Trac admin privileges as well, so that you can ravage the tickets and the wiki. Let me know if there is anything else I can do for you. I'll be checking the mailing lists from time to time, but one way to catch my attention in the case of emergency is to put me explicitly on CC. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.15 released
On Sun, 2015-11-08 at 21:33 +0100, Laurent Wandrebeck wrote: > First, thanks to all of you for that release. Bonsoir Laurent, Do you have a Trac account? If yes, then I can grant you wiki editing privileges, so that you can add it to this page and keep it up to date on your own, like our Debian packager: http://www.midnight-commander.org/wiki/Binaries I honestly meant to do this myself, but, of course, I didn't manage and then simply forgot about it :-/ -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc and me
On Sun, 2015-11-08 at 22:14 +0100, Egmont Koblinger wrote: > > My git knowledge is pretty accurately described by > http://xkcd.com/1597/ , so the first time I'll do that branching and > merging (esp. the latter) it'd be great if someone double checked on > me. Sure, I can try to find time to help... Are you on IRC? Otherwise, I've just revealed a magic trick to attract my attention by email. Some info is available from here: http://www.midnight-commander.org/wiki/GitGuideLines http://www.midnight-commander.org/wiki/WorkingGuideLines http://www.midnight-commander.org/wiki/Hacking > Also: What are the steps to be performed before/after a commit? You pretty much summed it up :-) Commit everything is a nice patch series to a topic branch, check tests & indentation, create tentative NEWS entry and push for review... > I mean, run the unittests (make tests -- that's it?), Yes, that's always a good idea. > check if the code is formatted (make indent -- correct?), Yes; in addition, Travis is supposed to do it when you push your feature branch, and inform by email if there is a problem. > update the NEWS file (how?), anything else? When the ticket it closed, it should be added to the news page: http://www.midnight-commander.org/wiki/NEWS-4.8.16 >From there, it makes it into the release NEWS; see the old one here: http://www.midnight-commander.org/wiki/NEWS-4.8.15 -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander 4.8.15 released
On Sun, 2015-11-08 at 22:08 +0100, Laurent Wandrebeck wrote: > > Yes, I have one, « low ». I’ll try to keep it up to date for > rh/fedora :) I hope it should work now! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Midnight Commander 4.8.15 released
Hi, We are glad to finally announce the release of mc-4.8.15! This new version brings several critical bugfixes to the search / find file functionality, as well as a large number of other fixes and improvements. Please note, that the minimum required version of glib is now 2.26.0! Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.15 I would like to thank everybody who contributed to this release (and, in particular, Andrew and Slava), including our dedicated translators! In other news, we are very happy to welcome a long standing contributor Egmont Koblinger as a new committer. We are very much in need for dedicated maintainers to carefully review and integrate user contributions, process bug reports and generally improve on our aging code base, and accepting a new committer is an important step towards improving current situation. Enjoy! -- 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
Re: Please release 4.8.15
On Thu, 2015-11-05 at 11:48 +0300, Slava Zanko wrote: > > I going to review cleanup branch and I'll help with releasing new > version. Great, would you find time this weekend? For me, Sunday would be best. It would be great if I could do it once together with you, and then maybe Egmont can go it once together with me the next time. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc and me
On Wed, 2015-11-04 at 22:09 +0100, Egmont Koblinger wrote: > getting to know the development process, policies (e.g. which changes > require approval, when to git branch, etc.), and Well, basically it's all about having a ticket & a topic branch per feature / non-documentation bugfix, where ticket number and summary are in the commit message along with a short description and a sign-off, and doing a --no-ff merge when it's finished (i.e. rebase first to keep the history nice and clean), see git log. Changes to the documentation, maintainer scripts, translations, etc. can go directly into master. There is more legalese on the trac at various stages of bitrot, but that's basically all that matters to me, I think. Does this sound reasonable to you? > requesting to get faster responses to my patches that require review – > or to be able to submit them if I don't get response in a certain > amount of time. Here comes the tricky part; the first rule was that the branch gets merged as soon as it gets 3 votes from the maintainers other than the main author, then it was quickly changed to 2 votes, and then eventually degraded into 1 vote, and then... then you know what happened. How about doing it the other way around from now on? You put the branch on review, and if there is no vote coming, and no one vehemently objects on technically substantiated grounds, it can go into master after 4 weeks, or I can rubber-stamp it if you want to keep the formalities :-) Does this sound reasonable? > keep doing what I did so far and do even more, but without > obligations. The obligations anyone here has are at best the "moral" ones. There is no signing of contracts involved in getting commit access. Only I'd expect you not wiping the repository after a tequila party, feeling responsible for fixing stuff you happened to break, being careful with the private keys if you need/want access to more infra, etc. and in general keep the pills handy. I don't think this would be a problem, would it? -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Please release 4.8.15
Hi Egmont, Sorry for failing to answer earlier, but I guess you know the current situation well enough anyways to not to require further explanations... On Tue, 2015-11-03 at 00:22 +0100, Egmont Koblinger wrote: > > Ping - any plans?? My plan is still to make a release from the current master as soon as I can get to it. The question is when this is going to happen. I've put aside some time from under the Christmas tree... whether I'll manage to beat this or not, I can't tell, but I'm honestly trying. > If there are 2-3 more fixes you'd like to sqeeze in, sure, go ahead > and apply them quickly (and please include #3534 as well). See comment therein... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Please release 4.8.15
On Sun, 2015-10-18 at 21:22 +0200, Egmont Koblinger wrote: > > Now that the infamous segfault is finally fixed, could we please have > a new release in the very near future? Hi Andrew, I'm generally happy with the current state of master, I only wanted to update the POT file again, so that translators can catch up if anything has changed. What are your plans? I've seen that Slava has been looking at the cleanup branch. It would be great if we can get this merged, and then I can try to cut a release, maybe assisted by Slava if he has time. Probably it would be better to go through the whole process at least once for someone other than Slava, even if he is able to make more time, given the circumstances... What do you think? Anything you'd absolutely like to get done before 4.8.15, anything I should focus on when I get a chance to help us to get there, eventually? -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Migration to Travis CI and help with tests
On Tue, 2015-11-03 at 08:20 +0100, Marco Ciampa wrote: > > Really really thanks for this. Hi Marco, I really wish I could get to it earlier, this is really long time overdue... but it's the way it is :-/ -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander not compiles on Debian Squeeze
On Tue, 2015-10-20 at 14:48 +0300, Mooffie wrote: > > You also need to update README, INSTALL, HACKING. Thanks! I would have forgotten about it. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander not compiles on Debian Squeeze
On Tue, 2015-10-20 at 14:13 +0300, Andrey Tataranovich wrote: > Glib version check patch attached. Thank you for the patch! Just hit master. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Midnight Commander not compiles on Debian Squeeze
On Mon, 2015-10-19 at 20:30 +0300, Andrey Tataranovich wrote: > > Glib version check should be introduced in this case. My opinion - if > configure completes without error, then compilation should go without > error too. Otherwise it is a FTBFS bug. Hi Andrey, If you can come up a one-liner patch to make it compatible with old glib, we can think of applying it; I have nothing against supporting older glib per se, unless it comes with too much of a maintenance cost... but I'm not really sure if it's worth it. Back when I was taking care of backporting mc to older RHELs, I simply used to build newer glib statically from within the package and link mc to it... that's the route I'd suggest you to go if you care about backporting mc to Squeeze. Hi Egmont, Could you please be so kind as to tell me what's the minimal version required now? I can look into bumping the version in the configure check... as soon as I manage to get to it :-/ Thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] isofs fix: do not skip all .dotfiles
On Thu, 2015-10-15 at 23:19 +0200, Denys Vlasenko wrote: > > https://www.midnight-commander.org/ticket/3537 Thank you! > > and if you can check when the > > second bug occurs, fix and test it, I will make a branch and merge > it... > > I fear you will ask me to create another ticket. You are most welcome to attach it to the same ticket. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH] isofs fix: do not skip all .dotfiles
On Thu, 2015-10-15 at 18:56 +0200, Denys Vlasenko wrote: > There appears to be an easy bug in iso9660 helper: Hi Denys, Could you please be so kind as to make a ticket and attach the patches for both changes there? Your first patch looks nice and simple, and if you can check when the second bug occurs, fix and test it, I will make a branch and merge it... Thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Call for help: Please test patch to 3449
On Sun, 2015-09-27 at 21:08 +0200, Egmont Koblinger wrote: > After 2 weeks of testing, the patch seems to be good. > > Dear devels, please apply it and release 4.8.15 in the very near > future, thanks! Hi Andrew, I've been using patched mc last week, and it seems stable. Could you please review and apply? Many thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
