From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: 48650@debbugs.gnu.org
Subject: [bug#48650] [PATCH] gnu: Add emacs-org-pandoc-import.
Date: Wed, 26 May 2021 14:43:48 +0200 [thread overview]
Message-ID: <87lf81is1n.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <347e7d7d2fca562cf038cc7acb3a203862397d7f.1621940480.git.public@yoctocell.xyz> (Xinglu Chen's message of "Tue, 25 May 2021 13:02:30 +0200")
Hello,
Xinglu Chen <public@yoctocell.xyz> writes:
> * gnu/packages/emacs-xyz.scm (emacs-org-pandoc-import): New variable.
Thank you. It looks good with one minor nit below.
> + (synopsis "Save yourself from non-Org formats")
> + (description "This package uses Pandoc to convert selected file types to
> +Org, so you never have to leave Org. There are two tiers of non-Org file
> +avoidance:
> +
> +@enumerate
> +@item The basic ``get me out of here'' ---
> +@code{org-pandoc-import-{to,as}-org} allows you to easily convert supported
> +non-Org files to an Org file/buffer with Pandoc
> +
> +@item The ``I don’t even want to see non-org files'' ---
> +@code{org-pandoc-import-transient-mode} is for you. What it does:
> +@itemize
> +@item (via file handlers) intercepts requests for non-Org files it knows it
> +can convert
> +@item uses @code{org-pandoc-import-to-org} to convert the file to a temporary
> +Org file
> +@item opens this Org file instead
> +@item exports back to the original non-Org file on save
> +@end itemize
> +@end enumerate")
Could you make the synopsis and the description more neutral? E.g., we
can drop the "so you never have to leave Org" part, etc.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-05-26 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 11:02 [bug#48650] [PATCH] gnu: Add emacs-org-pandoc-import Xinglu Chen
2021-05-26 12:43 ` Nicolas Goaziou [this message]
2021-05-26 14:11 ` Xinglu Chen
2021-05-26 14:16 ` Xinglu Chen
2021-06-02 19:52 ` bug#48650: " Nicolas Goaziou
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=87lf81is1n.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=48650@debbugs.gnu.org \
--cc=public@yoctocell.xyz \
/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/guix.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.