From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: obarray
Date: Sun, 15 Dec 2013 05:17:01 +0100 [thread overview]
Message-ID: <8738lurbmx.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.9271.1387072648.10748.help-gnu-emacs@gnu.org
Michael Heerdegen <michael_heerdegen@web.de> writes:
> That's all described very well in
>
> (info "(elisp) Creating Symbols")
Yes, that's true. The Elisp manual is great. Thank you,
all of you who wrote and/or provided feedback to that
great book. I'm actually reading it cover to cover as
we speak. But I haven't gotten that far.
I managed to print it after getting the info system to
work. Apparently I had to add "non-free" to the Debian
repos for the emacs24-common-non-dfsg to show up on
aptitude search. Non-Debian-free-software-guidelines! I
thought the GNU Emacs people were the
fanatics... perhaps I should switch team!
Speaking of the manual, is this correct?
> Ordinary text terminals have no way of generating
> non-ASCII control characters, but you can generate
> them straightforwardly using X and other window
> systems.
Remember this method in Linux:
control keycode 39 = U+010F # C-; - get 39 with keycode
# then update with
# loadkeys <file>
;; and then
(define-key input-decode-map [?\u010F] [C-semi-colon])
--
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united: http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2013-12-15 4:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 0:54 obarray Emanuel Berg
2013-12-15 1:14 ` obarray Juanma Barranquero
[not found] ` <mailman.9268.1387070101.10748.help-gnu-emacs@gnu.org>
2013-12-15 1:37 ` obarray Emanuel Berg
2013-12-15 1:56 ` obarray Michael Heerdegen
2013-12-15 1:59 ` obarray Juanma Barranquero
[not found] ` <mailman.9271.1387072648.10748.help-gnu-emacs@gnu.org>
2013-12-15 4:17 ` Emanuel Berg [this message]
2013-12-15 4:17 ` obarray Barry Margolin
2013-12-15 4:47 ` obarray Michael Heerdegen
2013-12-15 4:55 ` obarray Emanuel Berg
2013-12-15 6:04 ` obarray Barry Margolin
2013-12-15 17:43 ` obarray Emanuel Berg
2013-12-16 17:44 ` obarray Barry Margolin
2013-12-17 1:47 ` obarray Michael Heerdegen
[not found] ` <mailman.9442.1387244871.10748.help-gnu-emacs@gnu.org>
2013-12-17 2:11 ` obarray Emanuel Berg
2013-12-17 2:55 ` obarray Michael Heerdegen
[not found] ` <mailman.9452.1387248989.10748.help-gnu-emacs@gnu.org>
2013-12-17 3:01 ` obarray Emanuel Berg
2013-12-17 17:32 ` obarray Barry Margolin
2013-12-17 17:42 ` obarray Emanuel Berg
[not found] ` <mailman.9279.1387082898.10748.help-gnu-emacs@gnu.org>
2013-12-15 5:11 ` obarray Emanuel Berg
2013-12-15 5:36 ` obarray Emanuel Berg
2013-12-15 6:17 ` obarray Michael Heerdegen
[not found] ` <mailman.9283.1387088419.10748.help-gnu-emacs@gnu.org>
2013-12-15 17:51 ` obarray Emanuel Berg
2013-12-15 6:15 ` obarray Michael Heerdegen
[not found] ` <mailman.9282.1387088166.10748.help-gnu-emacs@gnu.org>
2013-12-15 17:47 ` obarray Emanuel Berg
2013-12-15 5:58 ` obarray Barry Margolin
2013-12-15 17:28 ` obarray Emanuel Berg
2013-12-17 14:38 ` obarray jack-mac
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=8738lurbmx.fsf@nl106-137-194.student.uu.se \
--to=embe8573@student.uu.se \
--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).