From: MON KEY <monkey@sandpframing.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6390@debbugs.gnu.org
Subject: bug#6390: Should not regexp-quote quote newline?
Date: Fri, 11 Jun 2010 16:09:13 -0400 [thread overview]
Message-ID: <AANLkTimiem0Hk5lOmIi1fDSWw0jJrn-iA-qfG6zd7CQ6@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilzshZqZPvpS9KIstOLIojxlptL_M1k2HbJ89v5@mail.gmail.com>
On Fri, Jun 11, 2010 at 12:43 AM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
>> Sure. I object on the grounds that what you propose is madness.
>
> I can see no objection at all. What is it?
>
You've confirmed my suspicion ;)
The objection is that what you propose is madness, i.e lunacy!
It is absolutely NTRT to interpolate any such chars routed through the
elisp printer simply b/c you disagree with how an ASCII standard
character has been historically (mis)interpreted. Its the _users_
prerogative to dictate her intention here; it certainly isn't yours,
or Microsofts', or Emacs'.
IMHO it would be _insane_ to replace "\f" linefeed with "\t"
Evaluate these to see why:
(progn
(insert-char 12 1)
(describe-char (1- (point))))
(progn
(insert-char 9 1)
(describe-char (1- (point))))
Among other things, you may notice the inserted glyph `^L' which is used
throughout Emacs as the default value for indication of page boundaries.
e.g. `page-delimiter' and her buddy `forward-page'...
Not only are you asking to have the form-feed value replaced with an entirely
different _non-visible_ character but you are asking to fundamentally alter the
semantics from:
"Occurences of this character indicate vertical movement of the
print-head at EOL"
to:
"Occurences of this character indicate tabbed horizontal movement at EOL"
Blech! Why would you want to do something so silly?
Check out this history of the form-feed and (one of) its early
intended applications:
:SEE (URL `http://www.rfc-editor.org/EOLstory.txt')
:SEE-ALSO (URL `http://en.wikipedia.org/wiki/Linefeed')
P.S. I've taken on faith that you aren't instead suggesting to replace
"\f" with the line tabulation char `^K' ASCII 11 e.g. (insert 11)
Which would make only slightly more sense than the folly you've proposed.
--
/s_P\
next prev parent reply other threads:[~2010-06-11 20:09 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 [this message]
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
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=AANLkTimiem0Hk5lOmIi1fDSWw0jJrn-iA-qfG6zd7CQ6@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=6390@debbugs.gnu.org \
--cc=lennart.borgman@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.
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.