From: Van L <van@scratch.space>
To: 34660@debbugs.gnu.org
Subject: bug#34660: 27.0.50; (eshell)Top > Commands > Invocation
Date: Tue, 26 Feb 2019 13:18:54 +1100 [thread overview]
Message-ID: <m2lg23gult.fsf@scratch.space> (raw)
Hello Emacs,
There is a problem with sentence (2) in paragraph (2) traced to
eshell.info, eshell.texi.
Can OpenAI's GPT2 improve that sentence in terms of aesthetic? [1]
[1] https://en.wikipedia.org/wiki/OpenAI#GPT2
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- quote from *info* (eshell) Invocation
The command can be either an Elisp function or an external command.
Eshell looks first for an *note alias: Aliases. with the same name as
the command, then a *note built-in command: Built-ins. or a function
with the same name; if there is no match, it then tries to execute it as
an external command.
-- quote ends
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- quote from eshell.info
The command can be either an Elisp function or an external command.
Eshell looks first for an *note alias: Aliases. with the same name as
the command, then a *note built-in command: Built-ins. or a function
with the same name; if there is no match, it then tries to execute it as
an external command.
-- quote ends
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- quote from eshell.texi
The command can be either an Elisp function or an external command.
Eshell looks first for an alias (@pxref{Aliases}) with the same name as the
command, then a built-in (@pxref{Built-ins}) or a function with the
same name; if there is no match, it then tries to execute it as an
external command.
-- quote ends
next reply other threads:[~2019-02-26 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 2:18 Van L [this message]
2019-02-26 5:00 ` bug#34660: 27.0.50; (eshell)Top > Commands > Invocation Glenn Morris
2019-02-26 5:05 ` Van L
2019-02-26 6:04 ` Eli Zaretskii
2019-02-26 6:43 ` Van L
2019-02-26 15:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lg23gult.fsf@scratch.space \
--to=van@scratch.space \
--cc=34660@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.