emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: example paper written in org completely
Date: Sat, 19 Jun 2021 02:21:18 +0200	[thread overview]
Message-ID: <trinity-78112df4-f06c-41ff-b3bb-8e44dae7a8bd-1624062078030@3c-app-mailcom-bs16> (raw)
In-Reply-To: <87r1gy21wj.fsf@gmail.com>

Currently texinfo uses tex as the underlying process to create the typeset
document.  After talking to Gavin Smith, for texinfo to be able to use latex,
would require using latex to print the document, which necessitates a new
implementation.  Do we have a latex implementation with the Official Gnu
Software?

Will see with Gavn what capabilities exist for algorithms constructs
and how far can we go before we require the package.  It would be beneficial
for me to know  how far we go with org before we require the package as well.

Felicitations
Christopher

> Sent: Saturday, June 19, 2021 at 11:02 AM
> From: "Tim Cross" <theophilusx@gmail.com>
> To: emacs-orgmode@gnu.org
> Subject: Re: example paper written in org completely
>
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > It is a good package, but since it is inactive, org-mode could assimilate
> > it so people can use it, rather than in the form of an external package.
>
> I don't see any advantage in doing this. It is simple to include the
> package. Furthermore, if we start to bundle it, we also take on more
> responsibility for ensuring it works etc. Besides, where do we then
> 'draw the line' - there are lots of additional and useful Latex
> packages, many of which are probably even more commonly used, such as
> some of the packages which extend/enhance tables, code listings, etc.
>
> >
> > Defining the structure of an algorithm in a document is of value.
> > Can one do something similar using current code or does the algorithmicx
> > package have some more pleasant capabilities?
> >
>
> The algorithmicx package does add some useful functionality wrt
> formatting algorithms, but only for Latex exports. Just
> bundling the latex package with org will not change the existing
> situation - it will still only be functionality available with latex
> exports. All it *might* do is remove the requirement to install the
> latex package and add it to your export headers.
>
> Having similar functionality which is back end agnostic and based on
> just org syntax would be useful for some users. However, this would
> involve re-implementation of what the latex package does in elisp and
> adding code to the export layer to interpret the new structures
> appropriately. The big question is whether anyone has sufficient
> interest and desire for this functionality to actually do the work.
>
> My gut feeling is that the number of people who need this functionality
> who are not satisfied witih the current situation is too small to reach
> the level of critical mass that would see this requirement realised.
>
> >
> >> Sent: Friday, June 18, 2021 at 8:04 PM
> >> From: "Eric S Fraga" <e.fraga@ucl.ac.uk>
> >> To: "Christopher Dimech" <dimech@gmx.com>
> >> Cc: "Emacs Org mode mailing list" <emacs-orgmode@gnu.org>
> >> Subject: Re: example paper written in org completely
> >>
> >> On Thursday, 17 Jun 2021 at 19:19, Christopher Dimech wrote:
> >> > The algorithmicx latex package has a very annoying licence, the LaTeX
> >> > Project Public License.  Although a free software license, it
> >> > incompatible with the GPL with many requirements.
> >>
> >> And?  I'm not sure of the relevance.  I use many LaTeX packages when
> >> writing.  Whether they are GPL or not is rather secondary, in my view.
> >>
> >> --
> >> : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-551-gf70e36
> >> : Latest paper written in org: https://arxiv.org/abs/2106.05096
> >>
>
>
> --
> Tim Cross
>
>


      reply	other threads:[~2021-06-19  0:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 12:06 example paper written in org completely Eric S Fraga
2021-06-17 12:51 ` Juan Manuel Macías
2021-06-17 13:38 ` Greg Minshall
2021-06-17 15:06   ` Eric S Fraga
2021-06-17 15:11   ` Eric S Fraga
2021-06-17 16:33   ` Uwe Brauer
2021-06-17 16:40     ` Eric S Fraga
2021-06-17 19:54       ` Uwe Brauer
2021-06-18  8:02         ` Eric S Fraga
2021-06-18 11:55           ` Uwe Brauer
2021-06-18 12:46             ` Eric S Fraga
2021-06-18 14:38               ` [longlines] (was: example paper written in org completely) Uwe Brauer
2021-06-18 15:00                 ` John Kitchin
2021-06-18 15:19                   ` Bruce D'Arcus
2021-06-18 16:30                     ` [longlines] Uwe Brauer
2021-06-24 22:09                       ` [longlines] Haider Rizvi
2021-06-18 16:38                     ` [longlines] Uwe Brauer
2021-06-18 15:23                 ` [longlines] Eric S Fraga
2021-06-18 23:26             ` example paper written in org completely Tim Cross
2021-06-19  9:58               ` Jeremie Juste
2021-06-19 13:12                 ` Eric S Fraga
2021-06-19 15:58                 ` Samuel Banya
2021-06-17 14:40 ` Samuel Banya
2021-06-17 16:31 ` Christopher Dimech
2021-06-17 16:42   ` Eric S Fraga
2021-06-17 17:04     ` Christopher Dimech
2021-06-17 17:19       ` Christopher Dimech
2021-06-18  8:04         ` Eric S Fraga
2021-06-18 13:45           ` Christopher Dimech
2021-06-18 23:02             ` Tim Cross
2021-06-19  0:21               ` Christopher Dimech [this message]

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=trinity-78112df4-f06c-41ff-b3bb-8e44dae7a8bd-1624062078030@3c-app-mailcom-bs16 \
    --to=dimech@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@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).