From: Joseph Vidal-Rosset <firstname.lastname@example.org>
To: Joseph Vidal-Rosset <email@example.com>,
Subject: Re: org-mode 9.3 links gnus
Date: Wed, 29 Jul 2020 13:50:59 +0200 [thread overview]
Message-ID: <CAD-VTcEhe0TThHaGukT8dyfd7JUt8L_hKV0ju+JD7avn-bTBiA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
You are probably right, I guess a change between 9.1 and 9.3 on this point.
I just downgraded to emacs 26.1 and to org-mode 9.1 because I also noticed
that org-export-head https://github.com/itf/org-export-head i.e. the org
blog exporter that I am using does not work with org-mode 9.3,
unfortunately, and Ivan has no time to adapt this tool to the last release
of org-mode. That's too bad...
Le mer. 29 juil. 2020 à 13:37, Eric S Fraga <firstname.lastname@example.org> a écrit :
> On Wednesday, 29 Jul 2020 at 12:01, Joseph Vidal-Rosset wrote:
> > (replace-match "gnus:\\[Gmail\\]/Tous les messages#"))
> I wonder whether you have too many \\ (or even any) in this and the
> similar replace-string that comes later? Why do you have these at all?
> The string argument to both replace-match and replace-string  is not
> a regexp so  do not mean anything special.
> Have you tried with just "gnus:[Gmail]/..."?
>  and according to the documentation, replace-string should only be
> used interactively and you should use replace-match instead.
> : Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-682-geac255
[-- Attachment #2: Type: text/html, Size: 2029 bytes --]
prev parent reply other threads:[~2020-07-29 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 10:01 org-mode 9.3 links gnus Joseph Vidal-Rosset
2020-07-29 11:37 ` Eric S Fraga
2020-07-29 11:50 ` Joseph Vidal-Rosset [this message]
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 \
* 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
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).