From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: stardiviner <numbchild@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] Changes to link syntax
Date: Mon, 18 Mar 2019 22:33:15 +0100 [thread overview]
Message-ID: <874l7zuauc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <8736nlkn6u.fsf@gmail.com> (stardiviner's message of "Mon, 18 Mar 2019 09:04:25 +0800")
Hello,
stardiviner <numbchild@gmail.com> writes:
> So I have to consider a safer and larger method to upgrade link. I can't
> manually open every Org files and run linter on them.
I already offered a function for replacing it in a file. You can wrap it
within a `dolist' on `directory-files-recursively'.
> (Maybe linter can run on Org files automatically in programtically
> way?)
When not called interactively, it returns a non-nil value if any error
is found. And you can call it on a limited set of checkers. Though,
I think the function I provided is better.
> Seems I can wait for better solution now.
I don't see any other solution.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-03-18 21:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 17:19 [ANN] Changes to link syntax Nicolas Goaziou
2019-03-10 20:02 ` Samuel Wales
2019-03-10 22:13 ` Amin Bandali
2019-03-12 13:44 ` Nicolas Goaziou
2019-03-10 23:00 ` Daniele Nicolodi
2019-03-11 16:35 ` Nicolas Goaziou
2019-03-11 17:06 ` Eric S Fraga
2019-03-11 17:31 ` Daniele Nicolodi
2019-03-11 17:27 ` Marco Wahl
2019-03-11 18:00 ` Diego Zamboni
2019-03-11 23:07 ` Nicolas Goaziou
2019-03-12 5:42 ` Diego Zamboni
2019-03-15 5:23 ` stardiviner
2019-03-15 10:55 ` Nicolas Goaziou
2019-03-18 1:04 ` stardiviner
2019-03-18 21:33 ` Nicolas Goaziou [this message]
2019-03-19 8:06 ` stardiviner
2019-03-15 11:55 ` Nicolas Goaziou
2019-03-26 9:08 ` stardiviner
2019-03-27 2:00 ` stardiviner
2019-04-02 21:16 ` Nicolas Goaziou
2019-04-07 11:20 ` stardiviner
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l7zuauc.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.com \
/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/org-mode.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).