Nicolas Goaziou writes:
> Also, I don't think LaTeX treats it as a block element.
> E.g.,
>
> text
> \[1+1=3\]
> text
>
> is a single paragraph in LaTeX.
Yes and no. LaTeX is a bit more complex and does not only see inline
or block elements. It has paragraph mode (and inner
Hi Adam,
> Sounds good to me.
Thanks :) it’s nice to get a second opinion.
All the best,
Timothy
Hi Adam,
> Sure, I’ve just pushed these commits:
Great! I’ve just taken a peek and it’s a clear improvement in my eyes .
> Note that, after I made the other changes, the links scattered around
> the page clashed very badly with the nice “Org green” and black theme,
> so I adjusted them as well
On 27/11/2020 23:32, Maxim Nikulin wrote:
Unordered lists are styled a bit incorrectly in the single-page org
manual. Compare e.g. "Installation" section:
https://orgmode.org/org.html#Installation
https://orgmode.org/manual/Installation.html#Installation
For some reason whole text of
Max Nikulin writes:
> Currently the problem exists e.g. for "Plain Lists" section
> https://orgmode.org/manual/Plain-Lists.html - OK
> https://orgmode.org/org.html#Plain-Lists - bold items with no markers
>
> Output of makeinfo changed a bit, so a pattern in a helper script
> postprocessing HTML
Bastien writes:
> Less code is less bug and less maintainance. So I'm considering
> moving these files to the new (unmaintained) org-contrib repo at
> https://git.sr.ht/~bzg/org-contrib:
I'm now discarding this call for help on updates.orgmode.org.
--
Bastien
Hi Adam,
> Maybe this is moot, since Bastien already added the link to the home
> page, but anyway…
>
> On the Contribute page, I’d be in favor of having some kind of
> heading, like “Source Code,” and listing the git URL in text for easy
> copying (i.e. not hiding the URL behind a descriptive
Ryan Scott writes:
>(default-directory
> -(or (and dir (file-name-as-directory dir)) default-directory))
> +(or (and dir (if (eq dir 'attach)
> +(org-attach-dir t)
> + (file-name-as-directory dir)))
> +
Jean-Christophe Helary writes:
> I'm trying to work with SourceHut (sr.ht) and right now they only accept
> Markdown syntax for their readme/wiki files.
Hi Jean-Christophe,
If this is just for SourceHut you can use an HTML export and upload it
via the API instead of committing a Markdown
On Sat, Oct 2, 2021 at 1:46 AM Kyle Meyer wrote:
>
> [reordering top-posting...]
>
> Bruce D'Arcus writes:
>
> > On Fri, Oct 1, 2021 at 8:33 AM Bruce D'Arcus wrote:
> >>
> >> It looks like that /etc/csl directory isn't included in the emacs source
> >> tree.
>
> > Actually, that whole etc
> do not see a reason for idiosyncrasy that markup intended to add LaTeX
> snippet that looks like exactly as LaTeX commands for this purpose and
> even actually preserved during export to LaTeX should have different
> semantics for Org parser.
The answer is that \[ \] can only occur inside
A general comment (heh) here. This is not a bug and not easily fixed.
Line comments are their own top level element distinct from
paragraphs. If you need something that fits in a paragraph you can use
@@comment:@@ at the start of a line.
I agree that it is annoying, but Org line comment syntax
Hi,
I have seen that `org-latex-polyglossia-language-alist' contains far
more languages than `org-latex-babel-language-alist'.
Well, if I'm not mistaken, the situation in the LaTeX ecosystem is this:
Polyglossia appeared as a babel replacement for XelaTeX and LuaLaTeX,
since babel, at that time,
Juan Manuel Macías writes:
> Well, if I'm not mistaken, the situation in the LaTeX ecosystem is
> this: Polyglossia appeared as a babel replacement for XelaTeX and
> LuaLaTeX, since babel, at that time, had no support for these two
> new Unicode based TeX engines.
And, as far as I remember,
Hi Nicolas,
> *snip lots of text*
Thanks for going through my points in detail. I think I understand your
perspective much better now. At this point though, I’m not really sure what to
make of `\[ ... \]', I now feel like it’s sitting in some sort of markup limbo
where it can’t be either fully
On 02/10/2021 18:24, Eric S Fraga wrote:
On Saturday, 2 Oct 2021 at 18:18, Timothy wrote:
I can’t help but think that this line of thinking is a bit of a trap, because
I think you're right. Nicolas's view that we should not think of org as
a front-end for LaTeX is probably more to the
On Friday, 1 Oct 2021 at 22:41, Nicolas Goaziou wrote:
> Yes: habit. Also, I don't think LaTeX treats it as a block element.
> E.g.,
>
> text
> \[1+1=3\]
> text
>
> is a single paragraph in LaTeX.
This is true and probably the most convincing argument in this debate.
I have no
Hi Eric,
>> text
>> 1+1=3
>> text
>>
>> is a single paragraph in LaTeX.
> This is true and probably the most convincing argument in this debate.
I can’t help but think that this line of thinking is a bit of a trap, because
what LaTeX’s idea of a paragraph does not line up with Org’s. I think
> On Oct 2, 2021, at 21:18, Morgan Willcock wrote:
>
> Jean-Christophe Helary writes:
>
>> I'm trying to work with SourceHut (sr.ht) and right now they only accept
>> Markdown syntax for their readme/wiki files.
>
> Hi Jean-Christophe,
>
> If this is just for SourceHut you can use an
Bastien writes:
Hi,
No Wayman writes:
The attached patch
I don't see a patch, can you resend it?
Apologies. Resent.
>From e5d1c6cc231363e20b378e082236af44ac717ccc Mon Sep 17 00:00:00 2001
From: Nicholas Vollmer
Date: Thu, 30 Sep 2021 16:07:15 -0400
Subject: [PATCH] org-src.el: Fix
Hej,
I have noticed that properties that stretch over multiple lines using
the :value+: syntax are ignored by org-element-property and therefore
also by e.g. org-export-get-node-property when exporting to ics via
ox-icalendar.el (see example below). I was wondering now whether this is
> On Oct 2, 2021, at 15:24, Ihor Radchenko wrote:
>
> Jean-Christophe Helary writes:
>
>> My follow-up question is, most of the ox-stuff seem to be installed by
>> default, as far as I can tell. Why is ox-md not ?
>
> Not most. The default export backends are:
>
>> org-export-backends is
I like Timothy's idea that \[ \] markup should behave like block-level
element rather than inline object. On the other hand, Nicolas convinced
me that the problem is not only with filling paragraphs in Emacs using
M-q and it requires change of Org grammar. That is why I do not think
that
Hi Adam,
>From the last few messages in this thread, I think we’ve reached agreement on
the changes. Would you like to go ahead?
All the best,
Timothy
Joseph Vidal-Rosset writes:
> I got the following backtrace:
Err... This looks strange. Can you try re-installing Org? Or otherwise
go to org-capture.el, M-x eval-buffer, and try to get backtrace again
(hopefully, it can become more readable then).
Best,
Ihor
Timothy writes:
> I think a “Source Code” header could make sense, with a link to the cgit page,
> git clone line, and maybe a sentence or on Savannah for the unfamiliar.
> Perhaps
> we could like to the org-contrib and website repos as well there?
Sounds good to me.
Hello,
Timothy writes:
> Is it? I can't use verbatim like this:
>
> =
> some
> verbatim
> text
> =
>
> but I can do
>
> \[
> some
> display
> equation
> \]
>
> It seems to me that \[ ... \] is already treated differently from other
> inline markup.
There is some misunderstanding here.
You
Hi,
I took the liberty of creating a new "archive" subdirectory in Worg to
preserve some obsolete content (like "Fireforg", an extension which its
Worg entry said hasn't been developed since 2009):
https://orgmode.org/worg/archive/index.html
The archive's index page is exported, but the linked
Max Nikulin writes:
> Unfortunately I have no idea how to get Message-ID having a link to
> particular message on lists.gnu.org without search by e.g. subject and
> author.
It can be parsed from the html. Something like below (it is my
home-made parser, but I think the idea should be clear):
Hi all,
as the subject says:
https://orgmode.org/contribute.html is very straightforward and
https://orgmode.org/worg/org-contribute.html is very complete.
I think we should merge both pages into worg/org-contribute.org,
the page that we recommand users to read in general.
The page would
Bastien writes:
Thanks -- it does not apply against the main branch, can you
rebase
and resend it?
Certainly. See attached.
>From 4971ceb26a1fb138f4eeddc1a569b5c4dd3f1859 Mon Sep 17 00:00:00 2001
From: Nicholas Vollmer
Date: Thu, 30 Sep 2021 16:07:15 -0400
Subject: [PATCH] org-src.el:
See attached.
>From 477f05274d2de75fc6d4761e6e6089f46e024f4e Mon Sep 17 00:00:00 2001
From: Nicholas Vollmer
Date: Thu, 30 Sep 2021 16:07:15 -0400
Subject: [PATCH] org-attach.el: Fix checkdoc warnings
* org-attach.el: Fix checkdoc warnings.
---
lisp/org-attach.el | 41
I have an `org-babel-execute` function for the Hy programming language that
seems to have partly broken when I upgraded Org (from 9.1.14 to 9.4.6). It has
code to write a plot to a file when a `:file` argument is given to the code
block. It returns `nil` in this case, and previously, Org would
Hi Max,
Max Nikulin writes:
> If you think that some patches improve the manual, feel free to apply
> ones that you like or to suggest better variants.
Applied, thanks a lot!
--
Bastien
Trevoke writes:
> I've looked at the code around adding a log-note and it looks like it might
> be automatable but there's a lot of pieces I don't know in there, so if
> there's a way to add just a state transition with a programmatically
> provided note, I'll take that, please :)
It may be
Would it be better then as a new option entirely that sets the default
directory to the attachment directory and results in attachment links for
any inserted paths that are under that?
The attachment link detection could possibly be default behavior for link
insertion, but i can imagine that
dalanicolai writes:
> As svg is just xml, for small sketches I would prefer to insert directly
> the xml
> into the org-buffer within an image block, in which I can quickly toggle
> showing
> the image using `C-c C-c` (or `org-toggle-inline-images`). Also, exporting
> such
> xml should work
Bodertz writes:
> As you can see, point is at the beginning of the line. I think it
> should be after the dash, as is the case when indenting plain list
> items.
The fix is attached.
Best,
Ihor
>From 63870bec28e59732cbbdf8b2534f6ece96e2d5d8 Mon Sep 17 00:00:00 2001
Message-Id:
Max Nikulin writes:
> I like Timothy's idea that \[ \] markup should behave like
> block-level element rather than inline object.
On the other hand, we will loose the ability to inline small parts of
math, that should be typeset as separate equation, like:
...text \[ 1+2=3 \] more text...
On Saturday, 2 Oct 2021 at 18:18, Timothy wrote:
> I can’t help but think that this line of thinking is a bit of a trap, because
I think you're right. Nicolas's view that we should not think of org as
a front-end for LaTeX is probably more to the point. As Stefan has
noted, how LaTeX processes
Looks good (on both large monitor and on my phone). Thank you!
--
: Eric S Fraga via Emacs 28.0.50, Org 9.5-g9a4a24
: Latest paper written in org: https://arxiv.org/abs/2106.05096
On Sat, Oct 2, 2021 at 1:24 AM Kyle Meyer wrote:
> Is there a reason to avoid updating to the latest version?
No; updating them makes sense.
Bruce
Uwe Brauer writes:
"CM" == Christian Moe writes:
>
>> Uwe Brauer writes:
>
>>> Hi
>>>
>>> Is it possible to have a header and footer in all pages when
>>> exporting to odt? I presume I have to use a odt style I create with
>>> Libreoffice/Openoffice?
>>>
>>> Thanks
>>>
>>> Uwe Brauer
>
Hi,
No Wayman writes:
> Apologies. Resent.
Thanks -- it does not apply against the main branch, can you rebase
and resend it?
--
Bastien
Hanno Perrey writes:
> Hej,
>
> I have noticed that properties that stretch over multiple lines using
> the :value+: syntax are ignored by org-element-property and therefore
> also by e.g. org-export-get-node-property when exporting to ics via
> ox-icalendar.el (see example below). I was
Bruce D'Arcus writes:
> On Sat, Oct 2, 2021 at 1:24 AM Kyle Meyer wrote:
>
>> Is there a reason to avoid updating to the latest version?
>
> No; updating them makes sense.
All right, thanks. I've updated these files to latest versions in
06ab36eb0.
On 02/10/2021 21:26, Ihor Radchenko wrote:
Max Nikulin writes:
Unfortunately I have no idea how to get Message-ID having a link to
particular message on lists.gnu.org without search by e.g. subject and
author.
It can be parsed from the html. Something like below (it is my
home-made parser,
Bruce D'Arcus writes:
> Sorry; I wasn't clear.
>
> What I meant is that etc/styles was also not synced.
Right, some of the non-lisp files get moved around directory-wise
between the Org and Emacs repos. Just in case it didn't stick out in
the snippets from my message upstream, the same files
Max Nikulin writes:
> On 02/10/2021 21:26, Ihor Radchenko wrote:
[...]
>> It can be parsed from the html. Something like below (it is my
>> home-made parser, but I think the idea should be clear):
>>
>> (org-capture-ref-set-bibtex-field :key (org-capture-ref-query-dom :tag 'form
>> :tag 'input
I have an `org-babel-execute` function for the Hy programming language that
seems to have partly broken when I upgraded Org (from 9.1.14 to 9.4.6). It has
code to write a plot to a file when a `:file` argument is given to the code
block. It returns `nil` in this case, and previously, Org would
> On Oct 2, 2021, at 16:44, Tim Cross wrote:
>
> Jean-Christophe Helary writes:
>
>> I'm trying to work with SourceHut (sr.ht) and right now they only accept
>> Markdown syntax for their readme/wiki files.
>>
>> Since I work in Emacs/org-mode to write my documents (and try to stick to
>>
Vladimir Nikishkin writes:
> Does anybody have a workaround for this?
Note that ox-bibtex is not a part of Org now. Maybe you try using new
org-cite syntax instead? It should support HTML natively.
Best,
Ihor
Hi Timothy,
Timothy writes:
> Great! I’ve just taken a peek and it’s a clear improvement in my eyes
> .
:)
>> Note that, after I made the other changes, the links scattered around
>> the page clashed very badly with the nice “Org green” and black theme,
>> so I adjusted them as well (as
Rodrigo Morales writes:
> #+BEGIN_EXAMPLE
> Non-existent agenda file ~/foo.org. [R]emove from list or [A]bort?
> #+END_EXAMPLE
Confirmed
No Wayman writes:
> Bastien writes:
>
>> Thanks -- it does not apply against the main branch, can you rebase
>> and resend it?
>
> Certainly. See attached.
Applied, thanks a lot!
--
Bastien
No Wayman writes:
> See attached.
Applied, thanks.
--
Bastien
Ihor Radchenko writes:
> Max Nikulin writes:
>
>> - I am in doubts whether "emacs -Q -L ~/src/org-mode/lisp" way to try
>> version from git is important enough for the manual. I have added a
>> separate patch however to discuss such change.
>
> I feel that it should not be in the manual.
Jean-Christophe Helary writes:
> My follow-up question is, most of the ox-stuff seem to be installed by
> default, as far as I can tell. Why is ox-md not ?
Not most. The default export backends are:
> org-export-backends is a variable defined in org.el.
>
> Value
> (ascii html icalendar
Jarmo Hurri writes:
> Greetings.
>
> I just installed (stable) 9.5. from GNU ELPA, and tried to see what my
> agenda for today looks like. The agenda is empty, and I got error
>
> Debugger entered--Lisp error: (invalid-function (date date))
>
> with backtrace
>
> (date date)()
>
> On Oct 2, 2021, at 16:00, Ihor Radchenko wrote:
>
> Jean-Christophe Helary writes:
>
>> Next (related) question:
>>
>> Why that ugly number in front of headers defined with in HTML ?
>
> I have little knowledge about HTML export... I blind guess is that you
> may disable
Jean-Christophe Helary writes:
> I'm trying to work with SourceHut (sr.ht) and right now they only accept
> Markdown syntax for their readme/wiki files.
>
> Since I work in Emacs/org-mode to write my documents (and try to stick to
> that),
> I'd like to know if there is an elegant way to
Hi Timothy,
On Fri, Oct 1, 2021 at 10:10 AM Timothy wrote:
>
> Hi Adam,
>
> > Just now I found myself needing to look up the URL of the Org git repo,
> > and it seemed a bit harder than it ought to be. It’d be nice if there
> > were a prominent “source code” link on the front page, but I
> On Oct 2, 2021, at 14:57, Protesilaos Stavrou wrote:
>
> On 2021-10-02, 14:20 +0900, Jean-Christophe Helary
> wrote:
>
>> I'm trying to work with SourceHut (sr.ht) and right now they only
>> accept Markdown syntax for their readme/wiki files.
>>
>> Since I work in Emacs/org-mode to
Jean-Christophe Helary writes:
> Next (related) question:
>
> Why that ugly number in front of headers defined with in HTML ?
I have little knowledge about HTML export... I blind guess is that you
may disable org-export-with-section-numbers
(see "14.1.5 Options for the exporters" section of
Hi Bastien,
On Sat, Oct 2, 2021 at 12:03 AM Bastien wrote:
>
> Hi Adam,
>
> Adam Porter writes:
>
> > Other FOSS projects's sites seem to make their source code repo links
> > very prominent; could Org's web site do that too? :)
>
> Done, let me know if it's good enough.
>
> I was missing this
Greetings.
I just installed (stable) 9.5. from GNU ELPA, and tried to see what my
agenda for today looks like. The agenda is empty, and I got error
Debugger entered--Lisp error: (invalid-function (date date))
with backtrace
(date date)()
Ihor Radchenko writes:
> spect...@mail.com writes:
>
>> In a preexisting org table, hitting can add a new, unintended column
>>
>> Bug: After the 2nd iteration, org adds a unintended new column. Further
>> iteration adds more columns.
>
> Confirmed
>
> The problem appears somewhere inside
On 01/10/2021 10:53, Jarmo Hurri wrote:
Bastien writes:
I just ran 'git pull' and got a warning and an error:
warning: redirecting to https://git.savannah.gnu.org/git/emacs/org-mode.git/
Your configuration specifies to merge with the ref 'refs/heads/maint'
from the remote, but no such ref was
Eric S Fraga writes:
Looks good (on both large monitor and on my phone). Thank you!
+1
--
Thomas S. Dye
https://tsdye.online/tsdye
Hi Timothy,
> │ \[
> │ not part of a paragraph
> │ \]
My point is that that parses first as a paragraph (check org-element-at-point).
\[ and \] would be meaningless if it did not first parse as a paragraph.
> I also don’t see how footnotes are analogous, as footnotes are placed in the
>
Tom Gillespie writes:
> But surely #+begin_export latex works with org-latex-preview? If not then
> that would be a feature request to org-latex-preview yes?
It might be possible, but I don’t think you can generally expect #+begin_export
latex blocks to be either previewable in isolation, or
Max Nikulin writes:
On 01/10/2021 10:53, Jarmo Hurri wrote:
Bastien writes:
I just ran 'git pull' and got a warning and an error:
warning: redirecting to
https://git.savannah.gnu.org/git/emacs/org-mode.git/
Your configuration specifies to merge with the ref
'refs/heads/maint'
from the
FYI. It seems we fixed the same issue half a year apart by chance..!
Maybe if we had a forge or smth this would have been solved already by Emily's
patch beginning 2021. One can always wish, right? ;-)
Best
Gustav
From: Bastien
Sent: Monday, September 27, 2021
Hi Tom,
> The answer is that can only occur inside paragraphs. The issues
> here are exactly the same as the issues for inline footnotes. Org gives
> us a bit more power, but not the full power because Org is Org, not
> Latex. Making available outside of a paragraph would be a massive
>
Hi All,
I intend to push this in the next few days, assuming I don’t get any feedback.
All the best,
Timothy
I just noticed one more thing, regarding ess-eval-visibly etc:
>> + (setq user-inject-src-param ess-inject-source)
>> (setq ess-eval-visibly nil)
>> + (setq ess-inject-source 'function-and-buffer)
>> (ess-eval-buffer nil))
>> - (setq ess-eval-visibly
Hi Timothy,
Timothy writes:
> From 9c34dd6aba62d734f6ae9aecaffa76a0250bf495 Mon Sep 17 00:00:00 2001
> From: TEC
> Date: Wed, 29 Sep 2021 21:29:27 +0800
> Subject: [PATCH] org: Don't change image size based on font size
>
> * lisp/org.el (org--create-inline-image): When `create-image' is
Bastien writes:
> Nitpick: I suggest shortening the ChangeLog part like this:
> *snip*
> The ChangeLog part should not be too verbose, you can add explanations
> after it.
Thanks Bastien, I’ll use that message when I push the commit .
All the best,
Timothy
Ihor Radchenko writes:
> Jarmo Hurri writes:
>
>> Greetings.
>>
>> I just installed (stable) 9.5. from GNU ELPA, and tried to see what my
>> agenda for today looks like. The agenda is empty, and I got error
>>
>> Debugger entered--Lisp error: (invalid-function (date date))
>>
>> with
Greetings.
I use ditaa with org on a regular basis. Now that ditaa.jar is out of
org 9.5, I need to cope with the situtation.
I see two options, and neither was successful today. This is sort of
what I was afraid of when I voted for keeping ditaa bundled with org.
1. I am running Fedora 34,
Kyle Meyer writes:
> Rudolf Adamkovič writes:
>
>> When I try to export HTML with APA/CSL citations (C-c C-e h o),
>> Emacs says:
>>
>>> The default CSL locale file
>>> /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/etc/csl/locales-en-US.xml
>>>
>>> doesn’t exist or
Hi Jeremie,
Many thanks for bringing this over the finish line! I'm very glad it
made it into Org 9.5.
All the tests passed on my end, and and I successfully ran a few async
R blocks without any issues.
I do have some suggestions for code style below. They apply to both the
original patch, as
Aloha all,
Worg footnotes are oddly formatted for me. I see the footnote
number on one line, then the footnote on the next line, like so:
1
Gnuplot manual downloads:
http://www.gnuplot.info/documentation.html
Do others see this, as well? Is there a fix?
All the best,
Tom
--
Thomas S.
Hi Stefan,
Stefan Nobis writes:
> And, as far as I remember, babel development had nearly ceased during
> that period.
>
> Since quite some years, the development has gained much more traction
> for babel and, as far as I read, babel is today as good or superior to
> polyglossia in many regards
Hi Jeremie and Chuck,
>> But changing to `:async yes', the error aborts in a way that omits the
>> output.
>
> Interesting, I haven't thought about errors cases enough. Async process
> will be on the 9.5 release and this issue will be next on the todo list.
> Many thanks again for the feedback.
Better solution found: quit sr.ht and move to a gitea implementation.
No hassle, org files are fully recognized.
Jean-Christophe
> On Oct 2, 2021, at 14:20, Jean-Christophe Helary
> wrote:
>
> I'm trying to work with SourceHut (sr.ht) and right now they only accept
> Markdown syntax for
Hi Thomas,
"Thomas S. Dye" writes:
> Worg footnotes are oddly formatted for me.
This should be fixed now.
See https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-gnuplot.html
Thanks!
--
Bastien
87 matches
Mail list logo
