From: Dmitry Gutov <dgutov@yandex.ru>
To: Andreas Abel <abela@chalmers.se>, 31796@debbugs.gnu.org
Subject: bug#31796: 27.1; dired-do-find-regexp-and-replace fails to find multiline regexps
Date: Tue, 24 Nov 2020 02:13:19 +0200 [thread overview]
Message-ID: <2c881d16-e7e7-833d-4287-95b152b305b8@yandex.ru> (raw)
In-Reply-To: <e637b0c0-25b3-8fd5-9e5a-b064b243c776@chalmers.se>
On 24.11.2020 01:49, Andreas Abel wrote:
> With a software as old as emacs the most important feature is
>
> 1. backwards-compatibility
>
> The second most important feature is
>
> 2. backwards-compatibility
>
> The third most important feature is
>
> 3. backwards-compatibility
No.
That's a road toward irrelevance.
> It is like with C and LaTeX. If you cannot ensure that things keep
> working as they did, don't change anything.
>
> Tramp? I had to google this term.
Tramp has been with us for ~20 years, and ~10 years a part of Emacs. It
has a significant number of users.
Anyway, that Tramp fix was a happy side-effect. Now that I think back,
the main reason was the switch to the new interface which removed the
default binding for tags-loop-continue (now called fileloop-continue).
Which made using dired-do-search a little less convenient, and people
asked for analogous commands which used the xref UI. The original
commands are still with us, though.
> How often do programmers work on their local files in their day-to-day
> business, how often with remote files via tramp?
>
> If you contribute a new feature for 0.1% percent of the use cases but
> disrupt something (even minor) for 99.9% of the use cases, then with an
> old tool like emacs the choice is: don't replace the old functionality
> with your new functionality.
>
> Just don't break things. Please.
I'm sorry for the inconvenience, really. But not being able to break
anything, even, is an ever-growing cost on keeping Emacs relevant toward
contemporary expectations, or otherwise making it better.
> If you want fancy functionality that works with remote files, this is
> fine. There are enough keys on the keyboard you can bind the new
> functionality to.
>
> Please don't break things that worked.
>
> There are gazillion emacs users out there that dread each new emacs
> version because it will break their setup, their workflows, their
> habits. We do not want to spend days after upgrades to get our work
> environment back.
But you still upgrade to the new version? Expecting something new from
it, right?
> We value stability and conservativity over everything else.
And then Emacs users get older, change jobs, or entirely leave the
profession. If Emacs stays as it was 30 years ago, it will appeal only
to users who started with it 30+ years ago. And many of those have
already left.
Emacs users are an admirably faithful bunch, but there are forces of
nature we have to contend with as well.
next prev parent reply other threads:[~2020-11-24 0:13 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 18:58 bug#31796: 26.1; dired-do-find-regexp-and-replace fails to find multiline regexps Žygimantas Bruzgys
2018-06-12 10:17 ` Noam Postavsky
2020-11-23 21:25 ` Dmitry Gutov
2020-11-23 9:09 ` bug#31796: 27.1; " Andreas Abel
2020-11-23 15:23 ` Eli Zaretskii
2020-11-23 16:16 ` Drew Adams
2020-11-23 21:22 ` Dmitry Gutov
2020-11-24 19:28 ` Juri Linkov
2020-11-24 20:12 ` Drew Adams
2020-11-25 7:31 ` Juri Linkov
2020-11-25 17:37 ` Drew Adams
2020-11-24 20:19 ` Eli Zaretskii
2020-11-24 20:31 ` Juri Linkov
2020-11-24 20:51 ` Drew Adams
2020-11-24 21:07 ` Eli Zaretskii
2020-11-25 7:28 ` Juri Linkov
2020-11-25 15:48 ` Eli Zaretskii
2020-11-25 20:18 ` Juri Linkov
2020-11-25 20:30 ` Eli Zaretskii
2020-11-29 2:30 ` Dmitry Gutov
2020-11-29 15:22 ` Eli Zaretskii
2020-11-23 21:28 ` Dmitry Gutov
2020-11-23 23:49 ` Andreas Abel
2020-11-24 0:13 ` Dmitry Gutov [this message]
2020-11-24 1:19 ` Dmitry Gutov
2020-11-24 15:16 ` Eli Zaretskii
2020-11-24 15:43 ` Dmitry Gutov
2020-11-24 16:35 ` Eli Zaretskii
2020-11-24 19:43 ` Dmitry Gutov
2020-11-24 20:16 ` Eli Zaretskii
2020-11-30 2:25 ` Dmitry Gutov
2020-11-30 8:49 ` Juri Linkov
2020-12-01 2:21 ` Dmitry Gutov
2020-12-01 8:39 ` Juri Linkov
2020-12-03 2:46 ` Dmitry Gutov
2020-12-06 21:00 ` Juri Linkov
2020-12-16 3:00 ` Dmitry Gutov
2020-12-16 20:32 ` Juri Linkov
2020-12-17 0:40 ` Dmitry Gutov
2020-11-30 15:30 ` Eli Zaretskii
2020-11-30 15:39 ` Jean Louis
2020-11-30 16:36 ` Eli Zaretskii
2020-11-30 15:42 ` Jean Louis
2020-12-01 1:23 ` Dmitry Gutov
2020-12-01 8:36 ` Juri Linkov
2020-12-01 15:20 ` Dmitry Gutov
2020-12-01 1:24 ` Dmitry Gutov
2020-12-01 5:20 ` Richard Stallman
2020-12-01 15:46 ` Eli Zaretskii
2020-12-02 4:26 ` Richard Stallman
2020-12-02 14:56 ` Eli Zaretskii
2020-12-02 17:17 ` Dmitry Gutov
2020-12-02 17:39 ` Eli Zaretskii
2020-12-02 17:43 ` Dmitry Gutov
2020-12-02 17:47 ` Eli Zaretskii
2020-12-03 5:26 ` Richard Stallman
2020-12-03 2:23 ` Dmitry Gutov
2020-11-24 19:29 ` Juri Linkov
2020-11-24 19:39 ` Dmitry Gutov
[not found] <<CADy8Bt=f=LOE6ODLhhW7ZS6qXRQCzd15Hd0eFKVO8qok98ni8w@mail.gmail.com>
[not found] ` <<10120030-8b8d-b702-add4-8f099f934ed5@chalmers.se>
[not found] ` <<91c98791-9df2-43ee-9aac-205c5b0de9c2@default>
[not found] ` <<87blfm6922.fsf@mail.linkov.net>
[not found] ` <<838saqtsm9.fsf@gnu.org>
2020-11-24 20:32 ` Drew Adams
[not found] ` <<87mtz64htw.fsf@mail.linkov.net>
[not found] ` <<831rgitqe2.fsf@gnu.org>
2020-11-24 21:35 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c881d16-e7e7-833d-4287-95b152b305b8@yandex.ru \
--to=dgutov@yandex.ru \
--cc=31796@debbugs.gnu.org \
--cc=abela@chalmers.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).