From: Ihor Radchenko <yantar92@gmail.com>
To: rms@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: mardani29@yahoo.es, stefankangas@gmail.com, ghe@sdf.org,
yarnton@tutanota.com, emacs-devel@gnu.org, eliz@gnu.org
Subject: Re: Emacs as a word processor
Date: Fri, 25 Dec 2020 13:17:50 +0800 [thread overview]
Message-ID: <875z4qzcox.fsf@localhost> (raw)
In-Reply-To: <E1ksekr-0002qB-FN@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> > > What about the UI developed by Prof. Kitchin [1]?
> > > [1] https://github.com/jkitchin/org-ref
>
> > I don't have an opinion on its UI, but last time I checked, I found this
> > package to have way too many dependencies (several of them literally
> > not necessary).
>
> Would you like to summarize in 10 lines what job it does?
If you are asking about what org-ref does (in regard to reference
management), I tried to list the most important (for me) features in my
other email. Copying the relevant part of the email below:
1. Incremental search across all the references by
title/author/publisher/keywords
2. Support of org-links with proper exporting (i.e., org links to
articles are replaced to \cite in LaTeX)
3. Auto-generating bibliography
4. Ability to insert links to non-org buffers (text style references in
emails/text documents or even reference pdfs as email attachments)
5. Auto-retrieving meta-data from URL or DOI
6. Bibliography notes
Best,
Ihor
next prev parent reply other threads:[~2020-12-25 5:17 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 18:22 Emacs as a word processor Gregory Heytings via Emacs development discussions.
2020-12-22 18:39 ` Eli Zaretskii
2020-12-22 19:28 ` Eli Zaretskii
2020-12-22 19:37 ` Lars Ingebrigtsen
2020-12-22 19:46 ` Stefan Monnier
2020-12-22 20:00 ` Eli Zaretskii
2020-12-22 19:32 ` Jean Louis
2020-12-22 19:41 ` Arthur Miller
2020-12-22 19:51 ` Jean Louis
2020-12-22 19:57 ` Arthur Miller
2020-12-22 20:07 ` Qiantan Hong
2020-12-22 20:43 ` Arthur Miller
2020-12-22 20:56 ` Gregory Heytings via Emacs development discussions.
2020-12-24 5:49 ` Richard Stallman
2020-12-24 20:57 ` chad
2020-12-25 4:37 ` Richard Stallman
2020-12-25 7:14 ` Emacs as a word processor (ways to convert Word/RTF proprietary files) Jean Louis
2020-12-25 8:15 ` Eli Zaretskii
2020-12-25 9:58 ` Jean Louis
2020-12-25 12:08 ` Eli Zaretskii
2020-12-25 13:11 ` Jean Louis
2020-12-25 13:39 ` Eli Zaretskii
2020-12-27 21:28 ` Tomas Hlavaty
2020-12-28 7:26 ` Jean Louis
2020-12-28 17:11 ` Drew Adams
2020-12-28 22:19 ` Tomas Hlavaty
2020-12-29 8:31 ` Jean Louis
2020-12-29 13:27 ` Tomas Hlavaty
2020-12-28 13:47 ` Eli Zaretskii
2020-12-28 19:12 ` Tomas Hlavaty
2020-12-25 13:23 ` Arthur Miller
2020-12-27 9:43 ` Jean Louis
2020-12-25 10:30 ` Yuri Khan
2020-12-26 10:23 ` Richard Stallman
2020-12-26 10:32 ` Sv: " arthur miller
2020-12-26 11:03 ` Yuri Khan
2020-12-26 11:53 ` Tomas Hlavaty
2020-12-26 12:19 ` Jean Louis
2020-12-27 5:38 ` Richard Stallman
2020-12-25 10:59 ` Tomas Hlavaty
2020-12-25 13:19 ` Arthur Miller
2020-12-25 14:44 ` Tomas Hlavaty
2020-12-25 19:41 ` Sv: " arthur miller
2020-12-25 21:08 ` Stefan Monnier
2020-12-26 10:13 ` Sv: " arthur miller
2020-12-27 21:08 ` Tomas Hlavaty
2020-12-25 13:49 ` Jean Louis
2020-12-25 15:02 ` Tomas Hlavaty
2020-12-26 6:34 ` Jean Louis
2020-12-28 11:44 ` Eric S Fraga
2020-12-28 12:22 ` Tomas Hlavaty
2020-12-28 12:37 ` Eric S Fraga
2020-12-28 16:25 ` Tomas Hlavaty
2020-12-29 10:10 ` Eric S Fraga
2020-12-28 13:37 ` [pandoc] (was: Emacs as a word processor (ways to convert Word/RTF proprietary files)) Uwe Brauer
2020-12-28 14:56 ` Stefan Kangas
2020-12-28 15:02 ` [pandoc] Uwe Brauer
2020-12-28 16:33 ` [pandoc] (was: Emacs as a word processor (ways to convert Word/RTF proprietary files)) Tomas Hlavaty
2020-12-28 17:07 ` [pandoc] Uwe Brauer
2020-12-28 18:11 ` [pandoc] Tomas Hlavaty
[not found] ` <X+Xv2f/sQzaWg/B0@protected.rcdrun.com>
2020-12-25 15:07 ` Emacs as a word processor (ways to convert Word/RTF proprietary files) Tomas Hlavaty
2020-12-26 6:35 ` Jean Louis
2020-12-27 21:14 ` Tomas Hlavaty
2020-12-28 1:39 ` Amin Bandali
2020-12-28 16:38 ` Tomas Hlavaty
2020-12-26 10:23 ` Richard Stallman
2020-12-26 10:45 ` Eli Zaretskii
2020-12-27 5:38 ` Richard Stallman
2020-12-26 16:12 ` Stefan Monnier
2020-12-27 5:40 ` Richard Stallman
2020-12-28 13:41 ` Uwe Brauer
2020-12-23 4:53 ` Emacs as a word processor David Masterson
2020-12-23 5:26 ` Christopher Dimech
2020-12-23 7:52 ` Jean Louis
2020-12-23 8:02 ` Jean Louis
2020-12-23 9:53 ` Arthur Miller
2020-12-23 1:48 ` yarnton--- via Emacs development discussions.
2020-12-23 2:29 ` Christopher Dimech
2020-12-23 2:53 ` Stefan Kangas
2020-12-23 7:25 ` Ihor Radchenko
2020-12-23 17:58 ` yarnton--- via Emacs development discussions.
2020-12-23 18:06 ` Stefan Monnier
2020-12-24 3:09 ` Ihor Radchenko
2020-12-25 4:31 ` Richard Stallman
2020-12-25 5:17 ` Ihor Radchenko [this message]
2020-12-25 5:18 ` Ihor Radchenko
2020-12-26 10:28 ` Richard Stallman
2020-12-26 11:30 ` Ihor Radchenko
2020-12-23 17:09 ` Kévin Le Gouguec
2020-12-24 5:47 ` Richard Stallman
2020-12-23 10:18 ` Arthur Miller
2020-12-23 4:21 ` Richard Stallman
2020-12-23 4:38 ` Christopher Dimech
-- strict thread matches above, loose matches on Subject: below --
2020-12-24 6:18 Pedro Andres Aranda Gutierrez
2020-12-24 6:24 ` Christopher Dimech
2021-02-01 17:00 James Lu
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=875z4qzcox.fsf@localhost \
--to=yantar92@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ghe@sdf.org \
--cc=mardani29@yahoo.es \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
--cc=yarnton@tutanota.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.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).