unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Cycle Org Shift Select
Date: Mon, 9 Nov 2020 21:35:14 +0100	[thread overview]
Message-ID: <trinity-cde94aa9-661a-4bc1-a343-1823993bb7db-1604954114528@3c-app-mailcom-bs07> (raw)
In-Reply-To: <87tutyguk0.fsf@web.de>

It can always start from the first item in the list.  Then I can
check if (eq last-command this-command).  That is, if the user calls
same command it will cycle.  Can start with the first item in the list,
and when I get to the last, get back to the beginning.


> Sent: Monday, November 09, 2020 at 9:10 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Cycle Org Shift Select
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > I have this code to cycle the Shift Select option for Org Mode.
> >
> > I am a little concerned that (nconc Shftsel Shftsel) will continually
> > append, rather than just cycle through the list.
> >
> > Looking for a better way to this job.
>
> What behavior do you want to get?  Do you want to cycling to start
> always from the same point and cycle only for repeated commands
> invocations?
>
> Or do you want to have a state remembered by the command (I guess so)?
> Should this then really be a global or a per-buffer or per-window state?
>
>
> Regards,
>
> Michael.
>
>



  reply	other threads:[~2020-11-09 20:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 15:23 Cycle Org Shift Select Christopher Dimech
2020-11-09 19:12 ` Noam Postavsky
2020-11-09 20:13   ` Michael Heerdegen
2020-11-09 20:26     ` Noam Postavsky
2020-11-09 20:31       ` Michael Heerdegen
2020-11-09 20:37         ` Noam Postavsky
2020-11-09 21:08           ` Michael Heerdegen
2020-11-09 21:19             ` Noam Postavsky
2020-11-09 20:40     ` Christopher Dimech
2020-11-09 20:42       ` Noam Postavsky
2020-11-09 20:52         ` Christopher Dimech
2020-11-09 20:53           ` Noam Postavsky
2020-11-09 21:20             ` Michael Heerdegen
2020-11-09 21:25               ` Noam Postavsky
2020-11-09 21:36                 ` Michael Heerdegen
2020-11-09 21:45             ` Christopher Dimech
2020-11-09 21:49               ` Noam Postavsky
2020-11-09 21:50               ` Michael Heerdegen
2020-11-09 21:59                 ` Christopher Dimech
2020-11-09 22:49       ` Christopher Dimech
2020-11-10  8:08         ` tomas
2020-11-10 10:17           ` Christopher Dimech
2020-11-10 11:10             ` Michael Heerdegen
2020-11-10 16:37   ` Drew Adams
2020-11-11 17:09     ` Drew Adams
2020-11-09 20:10 ` Michael Heerdegen
2020-11-09 20:35   ` Christopher Dimech [this message]
2020-11-09 21:18     ` Michael Heerdegen

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=trinity-cde94aa9-661a-4bc1-a343-1823993bb7db-1604954114528@3c-app-mailcom-bs07 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).