From: "rgb" <rbielaws@i1.net>
Subject: Re: looping cursor position in dired
Date: 17 Nov 2005 15:54:28 -0800 [thread overview]
Message-ID: <1132271668.212323.80520@o13g2000cwo.googlegroups.com> (raw)
In-Reply-To: mailman.15691.1132260814.20277.help-gnu-emacs@gnu.org
Sebastian Luque wrote:
> Hello,
>
> Before I start writing something too complicated, what is the best way to
> allow the cursor to loop through the dired buffer? i.e. if the cursor is
> at the end of the buffer and you hit [up] (dired-next-line), then the
> cursor would move to the first line; likewise for the opposite action.
>
> Thanks,
Yes it would be a shame if you did something complicated;)
(defadvice dired-next-line
(before my-buff-wrap activate compile) "With wrapping"
(when (eobp) (goto-char (point-min))))
(defadvice dired-previous-line
(before my-buff-wrap activate compile) "With wrapping"
(when (bobp) (goto-char (point-max))))
next parent reply other threads:[~2005-11-17 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.15691.1132260814.20277.help-gnu-emacs@gnu.org>
2005-11-17 23:54 ` rgb [this message]
2005-11-18 0:12 ` looping cursor position in dired Sebastian Luque
2005-11-17 20:47 Sebastian Luque
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=1132271668.212323.80520@o13g2000cwo.googlegroups.com \
--to=rbielaws@i1.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.
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).