unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ingo Menger <quetzalcotl@consultant.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Meta-Characters, Special Characters
Date: 31 May 2007 02:25:58 -0700	[thread overview]
Message-ID: <1180603558.683418.313690@q66g2000hsg.googlegroups.com> (raw)
In-Reply-To: <1180481373.651591.253210@i38g2000prf.googlegroups.com>

On 30 Mai, 01:29, x...@xahlee.org wrote:
> Will (aka weber) wrote:
>
> «
> [about the various ways to input or represent keystrokes and or non-
> printable characters in Emacs]
>
> As far as I can see in all those situations entering meta-characters
> is
> addressed in a different way which I find confusing, e.g.:
> a) <key> _or_ C-q <key>
> b) C-q C-[, C-q C-m, C-q C-j, C-q C-i
> c) \e, \r, \n, \t
> d) (define-key [(meta c) (control c) (tab c)] "This is confusing!")
> »
>
> None of this complexity is istrinsic.
>
> 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.
>
> « b) C-q C-[, C-q C-m, C-q C-j, C-q C-i»
>
> In this, the C-q is the keyboard shortcut to invoke the command quoted-
> insert, which will insert a literal character of whatever character
> you can type on your keyboard. So, for example, C-q followed by the
> tab key will insert a the non-printable character tab.
>
> When speaking of non-printable characters, the context is a character
> set standard. Implicitly, we are talking about ASCII, and this applies
> to emacs. Now, in ASCII, there are about 30 non-printable characters.
> Each of these is given a standard abbreviation, and several
> representations for different purposes. For example, ASCII 13 is the
> "Carriage return" character, with abbr code CR, and ^M as its control-
> key-input representation. (M being the 13th of the English alphabet)
>
> For the full detail, look at the table here:http://en.wikipedia.org/wiki/Ascii
>
> (Note: Emacs also have a general way to input non-printable characters
> of the unicode standard. See
> Emacs and Unicode Tipshttp://xahlee.org/emacs/emacs_n_unicode.html
> )
>
> « 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
> 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.

At least not in yours, it seems. You do not understand, that \n is not
a way to enter the newline character, but is a way to name the newline
character without actually using it right mow.
The difference between using a character and mentioning (i.e. speaking
about) a character did not come to your mind yet, did it?

> I do not know the history of these display representations. (hopefully
> someone will) It is my guess, that part of the reason for these, is
> that the unix text editor vi, doesn't have a general way to input non-

Type Ctrl+V when vi is in input mode and then type the character you
want.
But note that, in most languages, the string literals
  "Xah Lee
           knows not much"
and
  "Xah Lee\n knows not much"
are very different. In fact, some languages will not even recognize
the first one as string literal.
This, again, has to do with the fact, that string literals are a way
to *mention* charachters that the compiled programm will later *use*.

      parent reply	other threads:[~2007-05-31  9:25 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
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 [this message]

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=1180603558.683418.313690@q66g2000hsg.googlegroups.com \
    --to=quetzalcotl@consultant.com \
    --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).