all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Small correction to commit ae2463796f236b8ee2cef3b5e38bffa13abd2233
Date: Fri, 6 Sep 2024 10:13:20 +0200	[thread overview]
Message-ID: <CAO48Bk-fcTXM_unaShjtyrX7eZLpTuMkHLbR+zS3OJ+JhrJkSw@mail.gmail.com> (raw)
In-Reply-To: <87seufqws2.fsf@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 2753 bytes --]

Hi,

I've continued thinking about this and have come up with:

Make sure this
evaluation does not load any files, or call functions like
@code{posn-at-point} or @code{window-in-direction}, which themselves
evaluate the mode line, as doing so could cause infinite recursion.

or

Make sure evaluating @var{form} does not load any files, or call functions
like
@code{posn-at-point} or @code{window-in-direction}, which themselves
evaluate the mode line, as doing so could cause infinite recursion.

I personally would highlight this. Putting that in a separate paragraph may
help
or adding a bold *CAVEAT* before. My feeling is that being in the paragraph
dilutes the importance of this kind of advices, not only here, but also in
other
places in the manuals. I know this can may take long, but IMHO this would
improve
the manuals a lot.

Best, /PA

On Wed, 4 Sept 2024 at 17:11, Stephen Berman <stephen.berman@gmx.net> wrote:

> On Wed, 04 Sep 2024 15:55:29 +0200 Stephen Berman <stephen.berman@gmx.net>
> wrote:
>
> > On Wed, 04 Sep 2024 15:25:20 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >>> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> >>> Date: Wed, 4 Sep 2024 09:02:18 +0200
> >>>
> >>> >evaluation cannot load any files, nor calls functions like
> >>> >@code{posn-at-point} or @code{window-in-direction}, which themselves
> >>> >+evaluate the mode line, as doing so could cause infinite recursion.
> >>>
> >>> Shouldn't that be 'cannot load any files nor call functions'?
> >>
> >> No, because "calls" refers to 'evaluation", which is singular, not
> >> plural.
> >
> > The clause beginning with "nor" is a complement of "can", so the verb
> > must be a bare infinitive, i.e. "call" and not "to call", but also not
> > "calls", since that's not an infinitive form.  If you find "nor call
> > functions" hard to parse, the more explicit "nor can it call functions"
> > is an alternative.
>
> After seeing your new rewording, I see that my "more explicit"
> alternative phrasing is not good in the full sentence, which I didn't
> see when I responded (a correct alternative is "nor that it can
> call...", which sound somewhat stilted, or simply (and better) "and
> cannot call...").  (Your new rewording is fine, though I think "neither
> loads any files nor calls functions like..." might be understood to
> imply nothing else is excluded from evaluation, while with "does not
> load any files or call functions like..." that implication seems
> weaker.)
>
> Steve Berman
>


-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 3954 bytes --]

  reply	other threads:[~2024-09-06  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  7:02 Small correction to commit ae2463796f236b8ee2cef3b5e38bffa13abd2233 Pedro Andres Aranda Gutierrez
2024-09-04 12:25 ` Eli Zaretskii
2024-09-04 13:55   ` Stephen Berman
2024-09-04 15:11     ` Stephen Berman
2024-09-06  8:13       ` Pedro Andres Aranda Gutierrez [this message]
2024-09-06 11:04         ` Eli Zaretskii
2024-09-07  5:17           ` Pedro Andres Aranda Gutierrez

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAO48Bk-fcTXM_unaShjtyrX7eZLpTuMkHLbR+zS3OJ+JhrJkSw@mail.gmail.com \
    --to=paaguti@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.