Ryan Scott writes:
> I've been working through a few different approaches. What's shaping up is
> something more general, having a special value
> for directory parameters (i.e. 'attach) and auto-detection of link paths that
> are in the attachment directory.
> The latest iterations don't
Max Nikulin writes:
> If you submitted HTML file, you might suggest to open sources to make it
> obvious that the mistake was not intentional.
One day! The university system switches to a read-only mode at the end of every
week, and I cannot open-source anything for two years after the
Timothy writes:
> […] MathJax seems to take care of it […]
>From what I understand, MathJax does nothing, for it expects to exit inside of
>valid HTML.
> […] but it looks like MathJax is also fine with and . […]
Not that I know how ox-html works internally, but FYI, we can also use TeX's
Hi Bhavin,
Bhavin Gandhi writes:
> I second the mention of something like "Confirmed" instead of email
> headers. I recently started reading Org mode list, reproducing bug
> reports, and using email headers is something I haven't managed to do yet
> (pending as I'm yet to set up some email
Daniel Fleischer [2021-10-06 Wed 18:05] wrote:
> Only 30 out of the 122 Elisp files have a maintainer. I'm interested in
> maintaining one or more files but I'm not sure what it means. Can we
> make it clearer, as perhaps other people are interested and want to
> know.
Thanks Bastien for
Hi Ihor and Bastien,
On Thu, 7 Oct 2021 at 21:08, Bastien wrote:
> Ihor Radchenko writes:
>
> > We may want to put reference to Woof docs. Not all users are even able
> > to add headers to emails. Or we can simply recommend using word
> > "^Confirmed" in emails.
I second the mention of
On 05/10/2021 23:32, Ihor Radchenko wrote:
Max Nikulin writes:
I tried come up with the reason why org-no-popup was used in the initial
implementation. I think, the reason is avoiding situation like what you
may see after running
(let ((pop-up-frames t)) (funcall-interactively #'org-goto))
So,
Hi Ihor,
Ihor Radchenko writes:
> Some comments:
>
>>> If you can reproduce a bug, reply to the original poster and add
>>> X-Woof-Bug: confirmed to your mail headers, and the bug will then be
>>> shown on updates.orgmode.org.
>
> We may want to put reference to Woof docs. Not all users are
On 07/10/2021 20:05, Timothy wrote:
Org should rewrite < and > to and to avoid broken HTML, or as < and
in general.
I think we’ve drifted a bit to the differences in processing (where the `\( ...
\)'
vs `$ ... $' comments are most pertinent), but as you say for valid HTML < and >
should
Hi,
I often come across the following use case:
helm-locate leads me to a file named (for example) document.pdf, which
is in an attached folder of an Org node. I open the document and then I
would like to jump from there to the Org node. I don't know if anyone
has found any solutions for this or
Bastien writes:
> Perhaps you can still carefully proofread
> https://orgmode.org/worg/org-contribute.html and enhance it?
Some comments:
>> If you can reproduce a bug, reply to the original poster and add
>> X-Woof-Bug: confirmed to your mail headers, and the bug will then be
>> shown on
On Thursday, 7 Oct 2021 at 14:27, Uwe Brauer wrote:
> Yes, as the subject states org-->odt.
Ummm, yes, I guess subject lines should be read... sorry for the noise.
--
: Eric S Fraga via Emacs 28.0.60, Org release_9.5-63-g67b613
: Latest paper written in org: https://arxiv.org/abs/2106.05096
Hi Greg,
Greg Minshall writes:
> in the absence of any other volunteer, i'd be happy to produce a merge
> for review. (though it might take a few weeks.)
thanks a lot for volunteering, but I did the merge a few days ago.
Perhaps you can still carefully proofread
Hi Rudolf,
> I do not understand. As Max pointed out, inequalities break HTML export in
> and as well.
>
> Example:
>
> - a - b>a
>
> Org should rewrite < and > to and to avoid broken HTML, or as < and
> in general.
I think we’ve drifted a bit to the differences in processing (where the `\(
On Thu, 07 Oct 2021 08:28:03 -0400, Uwe Brauer wrote:
"JMM" == Juan Manuel Macías writes:
Uwe Brauer writes:
I searched about google, but it seems that the only way to have a 10 or
11 pt font size is, again, by using styles. Am I right?
Yes, you are right. Word processors handle
Uwe Brauer writes:
> Thanks, but it seems 11TeXpt-->10.95
>
> So it is not that different.
In typography it's a significant difference. It's not dramatic, but it
can produce different results in a book using the same body text and the
same line spacing, same margins, page dims. etc. Also TeX
Greg Minshall writes:
> oof. \(...\) is the way to go.
I do not understand. As Max pointed out, inequalities break HTML export in \(
and \) as well.
Example:
- \(aa\)
Org should rewrite < and > to and to avoid broken HTML, or as \lt{}
and \rt{} in general.
R+
--
"'Contrariwise,'
>>> "JMM" == Juan Manuel Macías writes:
> Uwe Brauer writes:
>> I searched about google, but it seems that the only way to have a 10 or
>> 11 pt font size is, again, by using styles. Am I right?
> Yes, you are right. Word processors handle paragraph and character
> styles. Anything that is not
>>> "ESF" == Eric S Fraga writes:
> On Wednesday, 6 Oct 2021 at 17:18, Uwe Brauer wrote:
>> I searched about google, but it seems that the only way to have a 10
>> or 11 pt font size is, again, by using styles. Am I right?
> Are you referring to the export of an org document? If so, what
hi, Bastien,
in the absence of any other volunteer, i'd be happy to produce a merge
for review. (though it might take a few weeks.)
cheers, Greg
> as the subject says:
>
> https://orgmode.org/contribute.html is very straightforward and
> https://orgmode.org/worg/org-contribute.html is very
Timothy,
> I’m thinking we should perhaps update the docs to more strongly
> recommend `\( ... \)' over `$ ... $'. So that someone coming from say,
> Markdown + $-math or (not-La)TeX doesn’t just go “cool, $ works, I’ll
> keep on using that”.
i think that would be a helpful change.
cheers, Greg
Hi Greg,
> oof. ... is the way to go.
I’m thinking we should perhaps update the docs to more strongly recommend `\(
... \)'
over `$ ... $'. So that someone coming from say, Markdown + $-math or
(not-La)TeX doesn’t just go “cool, $ works, I’ll keep on using that”.
All the best,
Timothy
Rudolf,
> FYI: I have just discovered that this bug screwed up a paper I
> submitted to university this week. In the paper, I wrote the
> following: "[…] every term $t\in{}q$ with $idf(t)>c$ for some constant
> $c$ […]", and the "idf(t) > c" part got exported as "idf(t)". I cannot
> fix the paper
Uwe Brauer writes:
> I searched about google, but it seems that the only way to have a 10 or
> 11 pt font size is, again, by using styles. Am I right?
Yes, you are right. Word processors handle paragraph and character
styles. Anything that is not styled is applied by direct formatting,
manually,
Confirmed: this version does not work for me either.
--
: Eric S Fraga via Emacs 28.0.60, Org release_9.5-63-g67b613
: Latest paper written in org: https://arxiv.org/abs/2106.05096
On Wednesday, 6 Oct 2021 at 17:18, Uwe Brauer wrote:
> I searched about google, but it seems that the only way to have a 10
> or 11 pt font size is, again, by using styles. Am I right?
Are you referring to the export of an org document? If so, what target?
LaTeX has LaTeX_CLASS_OPTIONS in which
26 matches
Mail list logo
