unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Michael Albinus <michael.albinus@gmx.de>,  emacs-devel@gnu.org
Subject: Re: master 55eabe96c9: ; Improve manual for Tramp kubernetes method
Date: Tue, 25 Oct 2022 17:48:42 +0200	[thread overview]
Message-ID: <87fsfb7vl1.fsf@gmail.com> (raw)
In-Reply-To: <CAP_d_8W0bXb74n0_r=52k2_UGvPSaMhNaoN2UHwp3piAFUyARQ@mail.gmail.com> (Yuri Khan's message of "Tue, 25 Oct 2022 22:43:07 +0700")

>>>>> On Tue, 25 Oct 2022 22:43:07 +0700, Yuri Khan <yuri.v.khan@gmail.com> said:

    Yuri> On Tue, 25 Oct 2022 at 21:51, Michael Albinus <michael.albinus@gmx.de> wrote:
    Yuri> +    […] It should
    Yuri> +    return a string which is used to check, whether the
    Yuri> +    configuration of the remote host has been changed (which
    Yuri> +    would require to flush the cache data).

    >> > Comma not needed?
    >> 
    >> Don't know. In the Tramp sources, both "check, whether" and "check
    >> whether" is used, so it is inconsistent at all :-) Let's keep it, until
    >> somebody teaches me to change it this way or the other in all places.

    Yuri> “whether the configuration <…> has been changed” is a subordinate (aka
    Yuri> dependent) clause. In English, those are separated with a comma only
    Yuri> when coming before the main clause. Here, it comes after the main
    Yuri> clause, so a comma looks like a Germanism.

True, but Iʼm more concerned about the "require to flush" bit, which
should be "require flushing" :-)


Robert
-- 



  reply	other threads:[~2022-10-25 15:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166637666472.14803.2269230477358344016@vcs2.savannah.gnu.org>
     [not found] ` <20221021182424.F0E84C00B0F@vcs2.savannah.gnu.org>
2022-10-22  9:53   ` master 55eabe96c9: ; Improve manual for Tramp kubernetes method Michael Albinus
2022-10-24 14:39     ` Filipp Gunbin
2022-10-24 15:07       ` Michael Albinus
2022-10-24 15:33         ` Michael Albinus
2022-10-24 18:54           ` Michael Albinus
2022-10-24 23:42             ` Filipp Gunbin
2022-10-25 14:50               ` Michael Albinus
2022-10-25 15:43                 ` Yuri Khan
2022-10-25 15:48                   ` Robert Pluim [this message]
2022-10-25 16:02                     ` Yuri Khan
2022-10-25 16:45                       ` Michael Albinus
2022-10-25 17:29             ` Filipp Gunbin
2022-10-25 17:48               ` Michael Albinus
2022-10-25 18:41                 ` Filipp Gunbin
2022-10-25 20:14                 ` Filipp Gunbin
2022-10-26 12:01                   ` Michael Albinus
2022-10-24 20:41         ` Filipp Gunbin
2022-10-24 22:49           ` Filipp Gunbin

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=87fsfb7vl1.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=yuri.v.khan@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).