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

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

Hi,

@Eli Zaretskii <eliz@gnu.org>
>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'?

Best, /PA

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)?

-- 
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: 2091 bytes --]

             reply	other threads:[~2024-09-04  7:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  7:02 Pedro Andres Aranda Gutierrez [this message]
2024-09-04 12:25 ` Small correction to commit ae2463796f236b8ee2cef3b5e38bffa13abd2233 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
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=CAO48Bk_7hG8YhCC2-D6Gg6HAGhQWYEb4v3kMKsvSk2wYz02+8g@mail.gmail.com \
    --to=paaguti@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).