unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joshua Cranmer <Pidgeot18@epenguin.zzn.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Meta-Characters, Special Characters
Date: Wed, 30 May 2007 01:44:15 GMT	[thread overview]
Message-ID: <PF47i.6966$3B1.2710@trnddc08> (raw)
In-Reply-To: <1180481373.651591.253210@i38g2000prf.googlegroups.com>

xah@xahlee.org wrote:
> Will wrote:
> «a) <key> _or_ C-q <key>»
> 
> The C-q (or, pressing the Control key down then type q) is the
> keyboard shortcut to invoke the command quoted-insert.  It is a
> general a way to allow you to input any non-printable characters. This
> facility usually don't exist in other text editors. In popular text
> editor such as Microsoft Word or Mac's Application, you usally bring
> up a window showing all the special characters, then press a button to
> insert the char you want.

I would not go so far as to call Microsoft Word and Mac's Application 
"popular text editor [sic]"; I believe the proper term is "WYSIWYG word 
processors." Try programming in Word and then see if you would still 
claim that it is a text editor.

> « b) C-q C-[, C-q C-m, C-q C-j, C-q C-i»
> 
> When speaking of non-printable characters, the context is a character
> set standard. Implicitly, we are talking about ASCII, and this applies

Not technically. Implicitly, on any *NIX machine newer than, say, 2000, 
it implicitly refers to Utf-8, and Windows on English (or other 
Latin-based configuration, presumably) it would be ISO-8859-1 or Cp1252.

> « c) \e, \r, \n, \t »
> 
> This is a ad-hoc set of input and display representation for a few non-
> printable characters. This set is started by the motherfucking unix

Watch your language here!
> tech geeking morons, and by its free and speedy nature as cigarette
> given to children, today has spread to many languages (Perl, Java, C+
> +, C#, Python, JavaScript ...) and is a de facto standard. The damage
> is to such a degree that the general concept of unprintable
> characters, their representation, and their method of input, all
> treated in one systematic, simple way, are not in the consciousness of
> average industrial programers.

Far from it. Excusing your depressing lack of hyphens and incorrect 
spelling of simple words, the slash-character is neither ad-hoc nor 
damage-inducing. Because there are several non-standard ways to input 
control codes (not non-printable; HT prints something as much as ' ' 
does), the people who wrote the original C specification (not "unix tech 
geeking [sic]") decided to include such control codes as standard 
character references. The use of '\' as a control character makes 
perfect sense, as it tends to be rarely used in everyday stuff, and it 
already is a control character (think macros). Many of the languages 
cited -- although, interestingly enough, not C -- take as their source 
the B/CPL syntax, a.k.a. C syntax, to provide a familiar backdrop to new 
programmers.

Finally, I would like to address your idiotic usage of newsgroups. You 
are cross-posting a message about EMACS syntax to two (2) emacs 
newsgroups, a LISP group (I can sort of understand that), and a Perl and 
Java newsgroup. Well, at least you're cross-posting.

  reply	other threads:[~2007-05-30  1:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 12:58 Meta-Characters, Special Characters Will
2007-05-29 14:12 ` weber
2007-05-29 23:29 ` xah
2007-05-30  1:44   ` Joshua Cranmer [this message]
2007-05-30  4:42     ` Gernot Hassenpflug
2007-06-02  3:18       ` Miles Bader
2007-06-02  6:18         ` Gernot Hassenpflug
2007-06-02  7:45           ` David Kastrup
2007-06-02 15:39             ` Gernot Hassenpflug
2007-06-02  7:23         ` Eli Zaretskii
     [not found]         ` <mailman.1490.1180769072.32220.help-gnu-emacs@gnu.org>
2007-06-02 15:41           ` Gernot Hassenpflug
2007-05-31  1:20   ` xah
2007-05-31  9:25   ` Ingo Menger

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='PF47i.6966$3B1.2710@trnddc08' \
    --to=pidgeot18@epenguin.zzn.com \
    --cc=blah@somewhere.invalid \
    --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).