unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: yow.c
Date: Tue, 13 Jun 2006 16:32:07 +0300	[thread overview]
Message-ID: <87irn51bjs.fsf@jurta.org> (raw)
In-Reply-To: <E1FpSbo-0004S8-DQ@fencepost.gnu.org> (Richard Stallman's message of "Sun, 11 Jun 2006 12:16:16 -0400")

>     > Unfortunately, we have to delete yow.lines as well.
>
>     ??? But yow.el uses that file.
>
> Yes, we should delete yow.el also, since it will be useless.  Would
> you please do it?

Please don't.  I use yow.el with a local file to print funny one-line
error messages, i.e. what I do is

  (fset 'undefined 'yow)
  (setq yow-file ".../talker.msg")

and when a wrong key is pressed in a read-only buffer, it displays a
misleading error message.  For instance, trying to visit a file in the
dired buffer with a wrong key may display such an error message:

  File not found. Should I fake it? (y/n)
or
  Close your eyes and press escape three times.

This is useful to always get ready for any surprise :-)

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2006-06-13 13:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04  3:26 yow.c Eli Zaretskii
2006-06-04  8:52 ` yow.c Andreas Schwab
2006-06-04 16:55 ` yow.c Richard Stallman
2006-06-09 17:57   ` yow.c Eli Zaretskii
2006-06-10 11:03     ` yow.c Richard Stallman
2006-06-10 11:53       ` yow.c David Kastrup
2006-06-11 10:28         ` yow.c Richard Stallman
2006-06-11 14:24         ` yow.c Randal L. Schwartz
2006-06-11 16:41           ` yow.c Drew Adams
2006-06-12  9:18           ` yow.c Richard Stallman
2006-06-10 21:20       ` yow.c Eli Zaretskii
2006-06-11 16:16         ` yow.c Richard Stallman
2006-06-13 13:32           ` Juri Linkov [this message]
2006-06-13 14:21             ` yow.c Sam Steingold
2006-06-13 14:51               ` yow.c Randal L. Schwartz
2006-06-13 18:13                 ` yow.c Eli Zaretskii
2006-06-13 18:21                   ` yow.c Randal L. Schwartz
2006-06-13 18:43                     ` yow.c Eli Zaretskii
2006-06-14 10:03                     ` yow.c Richard Stallman
2006-06-13 23:20             ` yow.c Richard Stallman
2006-06-15  2:05               ` yow.c Jay Belanger
2006-06-15  6:11                 ` yow.c Randal L. Schwartz
2006-06-16 19:18                   ` yow.c Jay Belanger
2006-06-17 17:57                     ` yow.c Richard Stallman
2006-06-19 17:36                       ` yow.c Jay Belanger
2006-06-19 23:19                         ` yow.c Richard Stallman
2006-06-20 11:45                           ` yow.c Randal L. Schwartz
2006-06-20 12:03                             ` yow.c David Kastrup
2006-06-20 12:30                               ` yow.c Randal L. Schwartz
2006-06-17 17:57                     ` yow.c Richard Stallman

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=87irn51bjs.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.
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).