From: Christopher Dimech <dimech@gmx.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: Cycle Org Shift Select
Date: Mon, 9 Nov 2020 23:49:33 +0100 [thread overview]
Message-ID: <trinity-2ad36cd3-10ca-4453-8974-c80cc868c2a3-1604962173537@3c-app-mailcom-bs07> (raw)
In-Reply-To: <trinity-dd397434-4815-4139-afdb-4208b55d2bee-1604954416670@3c-app-mailcom-bs07>
What is the meaning of the '.' in '#1=(nil t always . #1#)?
> Sent: Monday, November 09, 2020 at 9:40 PM
> From: "Christopher Dimech" <dimech@gmx.com>
> To: "Michael Heerdegen" <michael_heerdegen@web.de>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Cycle Org Shift Select
>
> It cannot be 'nil t always'. Got to introduce nil between
> t and always because the user will have no way to figure out
> if the Org Shift Select was changed.
>
>
> > Sent: Monday, November 09, 2020 at 9:13 PM
> > From: "Michael Heerdegen" <michael_heerdegen@web.de>
> > To: help-gnu-emacs@gnu.org
> > Subject: Re: Cycle Org Shift Select
> >
> > Noam Postavsky <npostavs@gmail.com> writes:
> >
> > > '#1=(nil t always . #1#)
> >
> > I once have been told that circular programs are problematic. Today I
> > would prefer the use of a (maybe buffer local) helper variable (or, if
> > it's only in my init file, simply maybe make the command a closure).
> >
> > Regards,
> >
> > Michael.
> >
> >
> >
>
>
next prev parent reply other threads:[~2020-11-09 22:49 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 [this message]
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
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-2ad36cd3-10ca-4453-8974-c80cc868c2a3-1604962173537@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).