From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: cipher <markus.doerschmidt@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Error message: <dead-tilde> undefined. What to do?
Date: Wed, 18 Jul 2007 21:23:29 +0200 [thread overview]
Message-ID: <A4905A60-F096-4697-A5EE-040698A97B38@Web.DE> (raw)
In-Reply-To: <1184756894.964924.132560@x35g2000prf.googlegroups.com>
Am 18.07.2007 um 13:08 schrieb cipher:
> What can I do?
Insert the right character! It is:
character: ~ (126, #o176, #x7e, U+007E)
For example: C-q 1 7 6 RET
Is the ~ on your keyboard a 'dead key,' i.e. is it producing the
character when you press an a, o, n, or SPC afterwards?
--
Mit friedvollen Grüßen
Pete
"What is this talk of 'release?' Klingons do not make software
'releases.' Our software 'escapes,' leaving a bloody trail of
designers and quality assurance people in its wake."
prev parent reply other threads:[~2007-07-18 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 11:08 Error message: <dead-tilde> undefined. What to do? cipher
2007-07-18 19:23 ` Peter Dyballa [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=A4905A60-F096-4697-A5EE-040698A97B38@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=markus.doerschmidt@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.
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).