From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: help-gnu-emacs@gnu.org, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: replacing endline
Date: Thu, 20 Apr 2006 18:11:25 +0200 [thread overview]
Message-ID: <4447B2AD.8070104@student.lu.se> (raw)
In-Reply-To: <87acagux25.fsf@gmail.com>
Fredrik Bulow wrote:
>>> I don't see why this behavior shouldn't be labeled as a bug.
>>>
>> if you label that behavior as a bug, then you have introduced two
>> "bugs", not just one. the first bug is in your mental model of how
>> emacs should work, and the second, the one labeled as suggested. if
>> you pre-emptively fix the first bug, perhaps the second bug will, as a
>> result, vanish as well.
>>
>> applying the above thought process to various behaviors, you may
>> be able to find and remove many bugs in the future. good luck!
>>
>> thi
>>
>
> Thanks for that totally uncalled for insult.
If thi thinks there are two bugs then I think there are three now since
I agree with Fredrik. Or should it maybe be four thi, if perhaps you are
a bit wrong too?;-)
>
> So once again, what is the good reason that (query-replace "\n" "#")
> behave differenty than calling the same function with its keybinding
> and providing it interactively with the same arguments?
>
I also have difficulties understanding the prompting in cases like this.
I have nothing against the "C-q C-j" solution but it is not the first I
think of. Is there any reason not to just convert the input as needed so
that it in the interactive case works as Fredrik and I expect it to do?
This would make it easier at least for relative beginners. Could it be
done in such a way that it is still easy for those who are accustomed to
the current behaviour?
next prev parent reply other threads:[~2006-04-20 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 0:18 replacing endline sarah.dzion
2006-04-20 1:15 ` Katsumi Yamaoka
2006-04-20 1:17 ` Ye Wenbin
2006-04-20 1:22 ` Fredrik Bulow
2006-04-20 1:44 ` Fredrik Bulow
2006-04-20 1:56 ` Fredrik Bulow
2006-04-20 6:32 ` Thien-Thi Nguyen
2006-04-20 14:43 ` Fredrik Bulow
2006-04-20 16:11 ` Lennart Borgman [this message]
2006-04-20 18:16 ` Eli Zaretskii
2006-04-20 23:38 ` B. T. Raven
[not found] ` <mailman.650.1145549499.9609.help-gnu-emacs@gnu.org>
2006-04-20 19:25 ` Harald Hanche-Olsen
2006-04-20 22:19 ` Lennart Borgman
2006-04-21 7:38 ` Eli Zaretskii
[not found] ` <mailman.671.1145571606.9609.help-gnu-emacs@gnu.org>
2006-04-21 6:52 ` Harald Hanche-Olsen
2006-04-21 0:53 ` Thien-Thi Nguyen
2006-04-20 10:21 ` Peter Dyballa
2006-04-20 18:54 ` kgold
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=4447B2AD.8070104@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).