From: Mike Kupfer <kupfer@rawbw.com>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: emacs-30 baaf97ce1a1: ; Fix some ungrammatical uses of "allows to"
Date: Fri, 30 Aug 2024 16:39:25 -0700 [thread overview]
Message-ID: <72715.1725061165@alto.camomileplus.org> (raw)
In-Reply-To: <875xrhafqg.fsf@zephyr.silentflame.com>
Sean Whitton wrote:
> On Fri 30 Aug 2024 at 10:18pm +03, Eli Zaretskii wrote:
> > You should have instead reworded the text to avoid the use of these
> > constructs, making the text more clear and side-stepping the issue of
> > "allow to" entirely.
>
> Well, in this, as you are a non-native speaker, your opinion on whether
> it's clear counts for more than mine. So I would be happy to put in the
> effort to try to make it clearer. However, I don't think I'm capable of
> doing a good job, because they all read perfectly fine for me.
I'll take a stab at it.
doc/emacs/anti.texi:
The command no longer allows the display of diffs between a file and
its auto-save file.
etc/NEWS:
This lets the user customize different switches...
etc/NEWS.29:
*** Users can commit a subset of changes in a diffs buffer.
This function provides a way to modify some or all of the settings of an
existing connection-local profile.
Specifying a cons as the FROM argument causes the measurement of text
to start from a specified amount of pixels above or below a position.
lib/cdefs.h:
ISO C99 lets you declare arrays...
lisp/tab-bar.el:
A button in the window allows for the restoration of the killed
buffer.
lisp/vc/vc-git.el:
When this variable is nil, and the log ends with a rename, a button
below the rename allows for the display of the log for the file name
before the rename."
Given Eli's comment about changes related to gnulib, I won't suggest
anything for gnulib-common.m4.
HTH,
mike
next prev parent reply other threads:[~2024-08-30 23:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 17:40 emacs-30 baaf97ce1a1: ; Fix some ungrammatical uses of "allows to" Eli Zaretskii
2024-08-30 18:14 ` Alan Mackenzie
2024-08-30 19:00 ` Eli Zaretskii
2024-08-30 21:09 ` Sean Whitton
2024-08-30 19:03 ` Sean Whitton
2024-08-30 19:22 ` Eli Zaretskii
2024-08-30 21:07 ` Sean Whitton
2024-08-30 23:22 ` [External] : " Drew Adams
2024-08-31 0:23 ` Po Lu
2024-08-31 6:26 ` Sean Whitton
2024-08-31 6:49 ` Gerd Möllmann
2024-08-30 19:00 ` Sean Whitton
2024-08-30 19:18 ` Eli Zaretskii
2024-08-30 21:00 ` Sean Whitton
2024-08-30 21:15 ` Ship Mints
2024-08-30 23:39 ` Mike Kupfer [this message]
2024-08-31 6:15 ` Sean Whitton
2024-08-31 6:54 ` Eli Zaretskii
2024-08-31 14:54 ` Mike Kupfer
2024-08-31 6:44 ` Eli Zaretskii
2024-09-01 10:20 ` Sean Whitton
2024-09-01 10:37 ` Eli Zaretskii
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=72715.1725061165@alto.camomileplus.org \
--to=kupfer@rawbw.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
/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).