all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: Re: rfn-eshadow
Date: Sat, 05 Jan 2008 00:54:45 -0500	[thread overview]
Message-ID: <E1JB1zZ-00067D-NS@fencepost.gnu.org> (raw)
In-Reply-To: <jwvhchu1f6e.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 03 Jan 2008 21:51:37 -0500)

    No, it is perfectly right for rfn-eshadow to treat it as a file name,
    since that's what rfn-eshadow is all about: to improve file-name entry.

I think you are right.  If the supposed URL is going to be interpreted
as a file name, then it is right for rfn-eshadow to treat it as a file
name too.

      parent reply	other threads:[~2008-01-05  5:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03  9:51 [jidanni@jidanni.org: ffap; prompt turns color misleadingly] Richard Stallman
2008-01-03 21:42 ` rfn-eshadow (Was: [jidanni@jidanni.org: ffap; prompt turns color misleadingly]) Juri Linkov
2008-01-03 22:12   ` rfn-eshadow Michael Albinus
2008-01-03 22:28     ` rfn-eshadow Juri Linkov
2008-01-04  2:51   ` rfn-eshadow Stefan Monnier
2008-01-04  9:51     ` rfn-eshadow Juri Linkov
2008-01-04 12:11       ` rfn-eshadow Michael Albinus
2008-01-04 21:52         ` rfn-eshadow Juri Linkov
2008-01-04 22:23           ` rfn-eshadow Michael Albinus
2008-01-05 10:36             ` rfn-eshadow Juri Linkov
2008-01-05 22:34               ` rfn-eshadow Stefan Monnier
2008-01-06 14:08                 ` rfn-eshadow Michael Albinus
2008-01-06 21:54                   ` rfn-eshadow Juri Linkov
2008-01-07  6:57                     ` rfn-eshadow Michael Albinus
2008-01-09  0:59                       ` rfn-eshadow Juri Linkov
2008-01-09  2:17                         ` rfn-eshadow Stefan Monnier
2008-01-09  8:13                           ` rfn-eshadow Michael Albinus
2008-01-05  5:54     ` Richard Stallman [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JB1zZ-00067D-NS@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.