GNU bug report logs - #23426
25.0.93; dired-do-find-regexp doesn't find newline

Previous Next

Package: emacs;

Reported by: Heinz Rommerskirchen <heinz <at> h-rommerskirchen.de>

Date: Mon, 2 May 2016 17:19:02 UTC

Severity: normal

Merged with 24305

Found in versions 25.0.93, 25.1

Done: Dmitry Gutov <dgutov <at> yandex.ru>

Bug is archived. No further changes may be made.

Full log


Message #112 received at 23426 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Drew Adams <drew.adams <at> oracle.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 23426 <at> debbugs.gnu.org, heinz <at> h-rommerskirchen.de, kaushal.modi <at> gmail.com
Subject: Re: bug#23426: 25.0.93; dired-do-find-regexp doesn't find newline
Date: Wed, 4 May 2016 19:28:07 +0300
On 05/04/2016 07:10 PM, Drew Adams wrote:
>>> Had you simply _added_ this feature and not usurped the existing
>>> bindings, you would likely have heard nothing from me about this.
>>> I have no objection to the _addition_ of another way to search
>>> and replace in Dired.
>>
>> That's very generous of you.
>
> I don't understand the hostility/sarcasm.

It is sarcasm. Designed to point out that your paragraph above is an 
empty statement.

Of course if a change has no bearing on any user's workflow except on 
those who choose to opt in, there is literally nothing for you to 
complain about. But there are fewer things to be happy about as well.

> It's a minor complaint: Keep the new feature, but please
> don't tread on existing keys and their features.  Not
> without a good reason, at least.  Is that too much to ask?

It is.

And if the complaint is minor, maybe spend less time arguing about it 
next time?




This bug report was last modified 8 years and 270 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.