unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Fredrik Bulow <kaliumfredrik@gmail.com>
Subject: Re: replacing endline
Date: Fri, 21 Apr 2006 00:43:46 +1000	[thread overview]
Message-ID: <87acagux25.fsf@gmail.com> (raw)
In-Reply-To: 7efyk8pxjz.fsf@ada2.unipv.it

>> 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. Of course, any bug can be
removed by changing your expectations on how a program should behave
to the way a program actually behaves. "It's not a bug that something
crashes, it is suppose to crash, and how do I know that? Well, I tried
and it crashed!." Usually, if something behaves in an unexpected way I
think it is a bug unless there is a good reason why the current
behaviour makes more sense than what I expected. I was kind of hoping
that someone would give me the good reason why there should be two
different behaviours.

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?

/Fredrik

  reply	other threads:[~2006-04-20 14:43 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 [this message]
2006-04-20 16:11       ` Lennart Borgman
2006-04-20 18:16       ` Eli Zaretskii
     [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 23:38       ` B. T. Raven
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=87acagux25.fsf@gmail.com \
    --to=kaliumfredrik@gmail.com \
    /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).