unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: [david.ponce@wanadoo.fr: Re: [quarl@cs.berkeley.edu: widget (or recentf)]]
Date: Sat, 29 Apr 2006 23:03:28 -0400	[thread overview]
Message-ID: <E1Fa2DY-0003iV-7f@fencepost.gnu.org> (raw)

------- Start of forwarded message -------
Date: Sat, 29 Apr 2006 11:54:49 +0200
From: David Ponce <david.ponce@wanadoo.fr>
MIME-Version: 1.0
To: rms@gnu.org
Cc: David Ponce <david@dponce.com>
Subject: Re: [quarl@cs.berkeley.edu: widget (or recentf)]
In-Reply-To: <E1FZgSg-0006Lw-2O@fencepost.gnu.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
	version=3.0.4

Hi Richard,

 > Could you please look at this?
 >
[...]
 >
 > When I use recentf, the widgets don't accept RET at the end of a
 > button, which has been annoying me for a long time.  Is this
 > intentional widget.el behavior?
[...]

For button widgets that represent files, that has been fixed by the
following change:

2006-04-03  Lennart Borgman  <lennart.borgman.073@student.lu.se>  (tiny change)

	* recentf.el (recentf-open-files-item): Include newline in button
	field, so opening a file will work, when the point is at the end
	of the file name.  Allow, for example, to [i]search a file by
	extension and just push RET to open it.

For other widget buttons this is the "normal" behavior, and IMHO not
an issue (for example, this is true in customize buffers too):

In a widget buffer, when the point is between the beginning and the
end of a button widget, then RET just works.  When the point is at the
end of a widget, it is not considered on the widget but just after it,
so RET will not work there.

I am not sure this behavior should be changed.

Sincerely,
David
------- End of forwarded message -------

                 reply	other threads:[~2006-04-30  3:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1Fa2DY-0003iV-7f@fencepost.gnu.org \
    --to=rms@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).