From: Eli Zaretskii <eliz@gnu.org>
To: "Garreau\, Alexandre" <galex-713@galex-713.eu>
Cc: contovob@tcd.ie, emacs-devel@gnu.org
Subject: Re: `call-process', to a string
Date: Tue, 30 Oct 2018 14:32:27 +0200 [thread overview]
Message-ID: <83y3afk42s.fsf@gnu.org> (raw)
In-Reply-To: <87lg6facvz.fsf@portable.galex-713.eu>
> From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
> Cc: contovob@tcd.ie, emacs-devel@gnu.org
> Date: Tue, 30 Oct 2018 12:32:16 +0100
>
> > "Point" only ever refers to Emacs buffers, never to anything else.
>
> Oh you’re right! Then with some context-sensitive deduction, you would
> guess DESTINATION as a buffer.
>
> However having to rely on deduction and context to understand a piece of
> doc looks silly, and if it does stuff with buffers it looks better to me
> to clearly have the word “buffer” within near. So I believe it is
> better with a such fix: thank you!
You are welcome. However, it's still worth to make yourself familiar
with "point" and its significance in Emacs, because you will see
similar text all over the place.
next prev parent reply other threads:[~2018-10-30 12:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 19:54 Automatically set eww-download-directory according xdg dir Garreau, Alexandre
2018-10-29 20:08 ` `call-process', to a string [Was: Re: Automatically set eww-download-directory according xdg dir] Garreau, Alexandre
2018-10-29 20:37 ` `with-temp-buffer', `with-output-to-string': `with-temp-buffer-to-string' / `with-current-buffer-to-string' [Was: Re: `call-process', to a string] Garreau, Alexandre
2018-10-30 2:26 ` Basil L. Contovounesios
2018-10-30 2:25 ` `call-process', to a string [Was: Re: Automatically set eww-download-directory according xdg dir] Basil L. Contovounesios
2018-10-30 3:59 ` `call-process', to a string Garreau, Alexandre
2018-10-30 7:19 ` `call-process', to a string [Was: Re: Automatically set eww-download-directory according xdg dir] Eli Zaretskii
2018-10-30 10:21 ` `call-process', to a string Garreau, Alexandre
2018-10-30 11:10 ` Eli Zaretskii
2018-10-30 11:32 ` Garreau, Alexandre
2018-10-30 12:32 ` Eli Zaretskii [this message]
2018-10-30 13:46 ` Garreau, Alexandre
2018-10-31 12:44 ` `call-process', to a string [Was: Re: Automatically set eww-download-directory according xdg dir] Basil L. Contovounesios
2018-10-30 6:57 ` Eli Zaretskii
2018-10-30 2:25 ` Automatically set eww-download-directory according xdg dir Basil L. Contovounesios
2018-10-30 3:57 ` xdg.el and eww custom load [Was: Re: Automatically set eww-download-directory according xdg dir] Garreau, Alexandre
2018-10-31 12:41 ` Basil L. Contovounesios
2018-10-31 22:52 ` Garreau, Alexandre
2018-11-01 14:29 ` Basil L. Contovounesios
2018-11-01 14:56 ` xdg.el and eww custom load Garreau, Alexandre
2018-11-01 18:54 ` Basil L. Contovounesios
2018-10-30 7:16 ` Automatically set eww-download-directory according xdg dir 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=83y3afk42s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=galex-713@galex-713.eu \
/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).