unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: YOW not fixed YET
Date: 15 Jul 2002 14:05:24 +0800	[thread overview]
Message-ID: <87hej1r0ez.fsf@jidanni.org> (raw)

I CANNOT believe this STILL isn't fixed.  I BET it is that ELI
character that HASN'T fixed it yet.  You see, I typed
<escape> x y o w <return> C-x <escape> <escape> <return>
and sure enough, I got my first YOW fix (as in "drug fix"), BUT NOT
THE SECOND!
-- 
http://jidanni.org/ Taiwan(04)25854780

             reply	other threads:[~2002-07-15  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15  6:05 Dan Jacobson [this message]
2002-07-15 19:31 ` YOW not fixed YET Alfred M. Szmidt
2002-07-15 20:07 ` Lute Kamstra
2002-07-16 12:33   ` Francesco Potorti`
2002-07-16 22:05     ` Lute Kamstra

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=87hej1r0ez.fsf@jidanni.org \
    --to=jidanni@dman.ddts.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).