unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: emacs-devel@gnu.org
Subject: Re: Minor feature idea
Date: Fri, 23 Jan 2015 10:41:56 -0600	[thread overview]
Message-ID: <87fvb18n57.fsf@red-bean.com> (raw)
In-Reply-To: <jwvd266uphs.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 22 Jan 2015 22:49:22 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Another option is to repurpose the word movement bindings. I don't know
>> what to think of that. Is a filename a "word"?
>
>No, words are smaller and have a well-defined meaning globally.
>OTOH "sexp" navigation is meant to be adjusted based on the particular
>syntax of the things being edited, so it fits very well with the idea of
>moving by file-name component.

Agreed -- this solution makes the most sense to me.

One doesn't see many files named "/home/jrandom/(cons foo bar)/qux" :-).

Using sexp motion to move by path component makes semantic sense, and anyway there is unlikely to be some other more useful interpretation of sexps in that context.



  parent reply	other threads:[~2015-01-23 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 22:09 Minor feature idea Richard Stallman
2015-01-22 22:56 ` Daniel Colascione
2015-01-22 23:07   ` Drew Adams
2015-01-23  3:43   ` Richard Stallman
2015-01-23  3:49   ` Stefan Monnier
2015-01-23  9:37     ` David Kastrup
2015-01-23 20:17       ` Stefan Monnier
2015-01-23 16:41     ` Karl Fogel [this message]
2015-01-23 17:45     ` Wolfgang Jenkner
2015-01-22 23:12 ` Dmitry Gutov
2015-01-23  3:44   ` Richard Stallman
2015-01-23 13:38     ` Andreas Schwab
2015-01-24  1:10       ` Richard Stallman
2015-01-25  6:45         ` Thierry Volpiatto
2015-01-26  3:42           ` Richard Stallman
     [not found] <<E1YEPwm-0004PK-Aw@fencepost.gnu.org>
2015-01-22 22:42 ` Drew Adams

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=87fvb18n57.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --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).