unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Documenting universal-async-argument
Date: Sat, 25 Aug 2018 13:12:27 +0200	[thread overview]
Message-ID: <87k1oebsys.fsf@gmx.de> (raw)
In-Reply-To: <831sawhpnm.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Aug 2018 20:24:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> +@deffn Command universal-async-argument
>> +This prefix command indicates the next command to run asynchronously.
>> +It is up to that next command to decide, what asynchronously means, or
>                                           ^
> This comma should be removed.
>
>> +@defvar universal-async-argument
>> +This is the controlling variable toggled by the
>> +@code{universal-async-argument} command.  If a command supports
>> +asynchronous behavior, it should check, whether the value of this
>                                          ^
> And this one.
>
>> +@deffn Command universal-coding-system-argument
>> +It is a prefix command to determine the coding system to be applied
>> +for the next I/O command.
>
> "This prefix command determines the coding-system to be used by the
> next I/O command."

Nobody else did comment, so I have pushed this to the
feature/tramp-thread-safe branch with the proposed changes.

> Thanks.

Best regards, Michael.



      reply	other threads:[~2018-08-25 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 12:00 Documenting universal-async-argument Michael Albinus
2018-08-07 15:53 ` Eli Zaretskii
2018-08-07 16:06   ` Michael Albinus
2018-08-07 16:27     ` Eli Zaretskii
2018-08-07 16:41       ` Michael Albinus
2018-08-17 15:02         ` Michael Albinus
2018-08-17 17:24           ` Eli Zaretskii
2018-08-25 11:12             ` Michael Albinus [this message]

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=87k1oebsys.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --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).