emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Matt Huszagh <huszaghmatt@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: incorrect documentation for file-desc header argument?
Date: Wed, 29 Jul 2020 08:41:37 +0100	[thread overview]
Message-ID: <87eeou4vke.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87ime6ap5p.fsf@kyleam.com> (Kyle Meyer's message of "Wed, 29 Jul 2020 01:03:30 -0400")

On Wednesday, 29 Jul 2020 at 01:03, Kyle Meyer wrote:
> So, I'd say this is a documentation bug.

Yes or else many of my org files would cease to work as intended!

: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-682-geac255

  reply	other threads:[~2020-07-29  7:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  4:35 Matt Huszagh
2020-07-29  4:50 ` Matt Huszagh
2020-07-29  5:03 ` Kyle Meyer
2020-07-29  7:41   ` Eric S Fraga [this message]
2020-07-30  1:19   ` Matt Huszagh
2020-07-30  2:29     ` Kyle Meyer

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eeou4vke.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=huszaghmatt@gmail.com \
    --cc=kyle@kyleam.com \
    --subject='Re: incorrect documentation for file-desc header argument?' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).