From: Lennart Borgman <lennart.borgman@gmail.com>
To: MON KEY <monkey@sandpframing.com>
Cc: 6390@debbugs.gnu.org
Subject: bug#6390: Should not regexp-quote quote newline?
Date: Mon, 14 Jun 2010 07:33:39 +0200 [thread overview]
Message-ID: <AANLkTimLW9lEcYl_qhBX9NrzO25-YGAO9bEJ07KQuBu6@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik_pskNTIYAY52ImChuO5MnqL5ek_LV7SKg6XP-@mail.gmail.com>
On Mon, Jun 14, 2010 at 5:00 AM, MON KEY <monkey@sandpframing.com> wrote:
> On Sat, Jun 12, 2010 at 9:28 AM, Lennart Borgman
> <lennart.borgman@gmail.com> wrote:
>>
>> I guess you mean "this is not what I thought you proposed".
>
> I meant what I wrote.
So you think you understood what I proposed better than me? That is
very strange.
>>> Regardless, the function name `print-escape-newlines' and its
>>> documentation SAY NOTHING ABOUT ESCAPING TAB CHARACTERS!!!!!
>>
>> Yes, it is a terribly bad name for the feature it provides.
>
> It is reasonably named, it says what it does.
> Prob. it is only terrible should one want \t escaped as well.
Why do you print-escape-newlines is a good name for something that
controls both escaping of newlines and form-feeds?
>> As I understand it the purpose of it is make all the
>> print/prin1/format/pp functions make the written representation of a
>> string easier to handle in certain cases.
>
> Understand whatever you want - this isn't what it
> `print-escape-newlines' _does_.
>
> You might find it exceedingly informative and interesting to look over
> Emacs sources from pre GNU days when coming to grips with the C
> vagaries inflicted on the Emacs read eval print loop.
Thanks, but no.
> Indeed, the transgression upon our poor (e)lisp REPL by the cult of the
> curly braced are many, and in the absence of a more maleable readtable
> and reader syntax she has been afforded little with which retaliate
> against the mighty C, his `\' escape syntax, and the hordes of bastard
> regexps his syntax has spawned.
Using the same character for read escapes and regexp backslash makes
things difficult, yes.
And lead to confusing discussions like this one.
>> but I can't think of a single reason why it should not be good to
>> handel TAB the same way in those cases.
>
> It is a mistake to extend your lack of foresight on other users of
> this feature.
>
>> Can you?
>
> Yes, I believe I can. So what?
It seemed important to you so I thought you might want to tell.
>> Don't you think getting a printed representation of this kind is useful.
>
> No, it is absolutely not useful for `print-escape-newlines' to do this.
>
> Yes, I might find it useful as a dedicated function under another
> name. Though I don't think it would be difficult to implement if/when
> needed, and it certainly doesn't need to be piggy-backed onto the
> existing feature.
I would be glad if you gave some arguments.
>> To clarify things I pointed to what Andreas wrote.
>
> Nonsense. This was your attempt to deflect my objection to one of your
> ill conceived proposals to another persons objection to yet another of
> your ill conceived proposals. IOW recursive nonsense...
Please don't waste our time! If you have something to say then do it!
> Which FWIW, is my principal objection to this and other such similar
> bug reports of yours. They often amount to nothing more than veiled
> feature requests which if presented/exposed/discussed as such would be
> received poorly.
I think it would be better if you asked me if you do not understand
them. There is no reason wasting other peoples time too. Mail me
privately.
> sender's subject line of such `bug report's are phrased in the
> form of a question which routinely match the pattern:
>
> "Should not the <FEATURE-X> .*?"
I am sorry, but you are misunderstanding. We also use the bug database
for wishes and suggestions so they do not get lost.
next prev parent reply other threads:[~2010-06-14 5:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 14:42 bug#6390: Should not regexp-quote quote newline? Lennart Borgman
2010-06-10 15:01 ` Andreas Schwab
2010-06-10 15:02 ` Lennart Borgman
2010-06-10 15:34 ` Drew Adams
2010-06-10 16:08 ` Andreas Schwab
2010-06-10 16:11 ` Lennart Borgman
2010-06-10 16:22 ` Andreas Schwab
2010-06-10 16:46 ` Lennart Borgman
2010-06-10 17:03 ` Andreas Schwab
2010-06-10 18:07 ` Lennart Borgman
2010-06-10 23:11 ` Lennart Borgman
2010-06-11 0:44 ` Lennart Borgman
2010-06-10 15:22 ` Drew Adams
2010-06-10 15:34 ` Lennart Borgman
2010-06-10 16:28 ` Juanma Barranquero
2010-06-10 16:47 ` Lennart Borgman
2010-06-10 16:56 ` Andreas Schwab
2010-06-10 17:00 ` Lennart Borgman
2010-06-11 4:19 ` MON KEY
2010-06-11 4:43 ` Lennart Borgman
2010-06-11 20:09 ` MON KEY
2010-06-11 20:37 ` Lennart Borgman
2010-06-12 6:18 ` MON KEY
2010-06-12 13:28 ` Lennart Borgman
2010-06-14 3:00 ` MON KEY
2010-06-14 5:33 ` Lennart Borgman [this message]
2010-06-12 6:51 ` Kevin Rodgers
2010-06-12 13:37 ` Lennart Borgman
2011-07-09 5:30 ` Glenn Morris
2011-07-09 10:03 ` Lennart Borgman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimLW9lEcYl_qhBX9NrzO25-YGAO9bEJ07KQuBu6@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=6390@debbugs.gnu.org \
--cc=monkey@sandpframing.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.