unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Small correction to commit ae2463796f236b8ee2cef3b5e38bffa13abd2233
Date: Wed, 04 Sep 2024 15:25:20 +0300	[thread overview]
Message-ID: <86jzfr61xr.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk_7hG8YhCC2-D6Gg6HAGhQWYEb4v3kMKsvSk2wYz02+8g@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Wed, 4 Sep 2024 09:02:18 +0200)

> 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.

> PS: @list I was just listing to the 'allow ...' discussion and you may have overseen that allow + infinitive is the 1:1
> translation of 'permitir + infinitive' in Spanish ;-) 
> Anyhow, my question would be if we always need 'allowing' or if we can say that "variables _control_ how things
> are done" and functions _do_ things. Wouldn't that be easier to read (and understand)?

Yes, where "controls" is appropriate.  It isn't always.  Here's one
random example:

  Turning on option 'foo' allows you to observe a wonderful vista.

Thanks.



  reply	other threads:[~2024-09-04 12:25 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 [this message]
2024-09-04 13:55   ` Stephen Berman
2024-09-04 15:11     ` Stephen Berman
2024-09-06  8:13       ` Pedro Andres Aranda Gutierrez
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

  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=86jzfr61xr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=paaguti@gmail.com \
    /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).