Re: Heading toward Org 9.5
Hi Pankaj, On Wed, Sep 22, 2021 at 5:21 PM Pankaj Jangid wrote: > Is there a page where I can see the changes when moving from 9.4 to > 9.5. Like etc/ORG-NEWS ? http://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS You can see it on the web but it's much more present to use Org Mode for obvious reasons. Best, -- yashi
Re: [ANN] org-ql 0.6 released
Juan Manuel Macías writes: > Hi Adam, > > Thank you very much for this great package. I could no longer live without > org-ql/helm-org-ql :-) Hi Juan, Thanks for the kind words. I'm glad it's useful to you. :)
Re: [PATCH] Fix some typos
Hi all: Max Nikulin writes: > Please, forgive my ignorance of Shakespeare's poetry. > > On 17/09/2021 17:05, Marco Wahl wrote: >>> On 17/09/2021 04:40, Stefan Kangas wrote: >> Please find attached another clean-up patch that fixes a small number of typos. > > Thou shall not change "memeory" to "memory" tho > I think, a bit more is required to avoid recurring attempts to change > spelling if you would like to see such variant. Static code analyzers > usually have a feature that allows to ignore specific warning at a > particular line, see e.g. > https://flake8.pycqa.org/en/latest/user/violations.html#in-line-ignoring-errors > for Python's flake8. > > Maybe "LocalWords:" could do a similar trick for ispell.el at least > for the whole file. Unsure if it is possible to add an exception for > the quote only. > > However there is namely "memory" in the "1609 Quarto", see e.g. > https://en.wikipedia.org/wiki/Sonnet_1 Web pages with the same variant > as in the Org manual do not mention the source (particular edition). I > hope, I just do not know what is considered as the canonical variant > for not so old language. I am not an expert on Shakespeare's poetry either, but as the author of the patch where Sonnet 1 is included, I can say that 'memeory' is a typo (sorry). At least I didn't use that word intentionally. I don't know if there is any textual variant 'memeory', but in my case it is nothing more than a simple typo :-). Best regards, Juan Manuel
Exporting: how to exclude top/bottom hline for tables?
Is there a way to exclude the top and bottom hline of tables during export? When I'm exporting to UTF-8, the top and bottom lines of the tables do not display correctly for me. Though the number of chars is correct, the face used by emacs does not match the face used for the rest of the file. So, I'd simply exclude those hlines. Is there a way to exclude those? Thanks,
Re: [PATCH] ox.el: add smart quotes for Greek
Max Nikulin writes:
> I believe, the patch is an improvement. It would be nice to have a
> comment clarifying the choice of secondary opening quote mark, but it
> is not required. It seems there is no recommendations or established
> practice for documenting of such decisions. I have not tested the
> patch though.
Since it's a "orthotypographical" addition, where there is a reasonable
doubt in one of the characters, I agree that a minimal explanatory note
in the commit message would be desirable. But it would have (IMHO) to be
something very brief.
>> -`org-export-smart-quotes-alist' and `org-export-dictionary'.
>> +`org-export-smart-quotes-' and `org-export-dictionary'.
>
> It it intentional change? I have not found other variables having the
> same prefix.
Oh, sorry. It's a horrible typo: I modified that part involuntarily, and
I didn't see it :-(.
> That character could get better support in future. I know, such chance
> is almost improbable, but imagine, a person familiar with the paper of
> Haralambous would consider change of the quote mark in question
> believing that Org developers were not aware of the "right" symbol. A
> comment in the source code may provide a hint that the choice was conscious.
>
> I forgot to mention it in my message from 2020-08-15 that I did not
> find the U+201F character in TeX pre-unicode LG* encodings for Greek.
In fact, the character is only problematic in pdfTeX. In XeTeX and
LuaTeX there is no problem, and you can also use the csquotes package.
But in pdfTeX you can't even get it with the
\usepackage[utf8x]{inputenc} option, which is to be expected, since
Unicode support of imputenc is very limited. LuaTeX is the natural
replacement for pdfTeX, but at the moment we have to maintain backward
compatibility and I can't find a way to represent that character in
pdfTeX. This second level quotes issue is not mentioned by Apostolos
Syropoulos in the babel greek documentation:
(https://www.ctan.org/pkg/babel-greek). There is probably no support for
this character in babel-greek.
Before uploading a corrected version of the patch (with a small
explanatory note), I could consult Haralambous himself by mail, and ask
him what he thinks of this question...
Best regards,
Juan Manuel
LaTeX mysteries
Hi, Max. Usually external LaTeX compilation is better. Its logs are more helpful too. But yet I don't know why I can't compile LaTeX in one PC or why previewing doesn't work. Probably some step by step guides for Windows users are necessary for these and other setting problems. Thanks for your advice! Sep 21, 2021 18:02:36 emacs-orgmode-requ...@gnu.org: > > Message: 1Date: Mon, 20 Sep 2021 23:41:20 +0700From: Max Nikulin > To: emacs-orgmode@gnu.orgSubject: Re: Emacs-orgmode > Digest, Vol 187, Issue 19Message-ID: > Content-Type: text/plain; charset=utf-8; > format=flowed > On 20/09/2021 00:16, Ypo wrote: >> >> Then I think I will behave like grown people and use LaTeX syntax, >> previewing it on HTML exports, cause it gives no errors compared to the >> problematic PDF exports. > > I never considered HTML as a viable preview option for LaTeX equation,so > thanks for the idea. In the past working LaTeX was anyway requiredsince > otherwise latex2html perl script could not generate images forequations. Web > changed since that times (some sites created by peopleunaware of LaTeX even > required activeX to display math). > Maybe your problem with PDF export is not so serious, e.g. pdflatexbinary is > not in PATH or some LaTeX package is missed. Have you tried toexport to LaTeX > file and to run pdflatex from command line to get errormessages?
Re: [PATCH] ox.el: add smart quotes for Greek
I believe, the patch is an improvement. It would be nice to have a comment clarifying the choice of secondary opening quote mark, but it is not required. It seems there is no recommendations or established practice for documenting of such decisions. I have not tested the patch though. -`org-export-smart-quotes-alist' and `org-export-dictionary'. +`org-export-smart-quotes-' and `org-export-dictionary'. It it intentional change? I have not found other variables having the same prefix. On 22/09/2021 03:20, Juan Manuel Macías wrote: [...] Possible options: - Add the note directly to the .el file. I am afraid, as inline comment it could be considered too long. - To a file in the "doc" directory dedicated to such decisions (there is no such file yet however) with a reference from the .el file. - Commit message. It is acceptable but not apparent for a person who reads the code that git log may provide detailed explanation of particular choice. ... Haralambous is a great TeX guru, and a great scholar and theorist of Greek typography, but... I would say that in this case his mind is more focused on a historical tradition probably abandoned before the digital age. That character could get better support in future. I know, such chance is almost improbable, but imagine, a person familiar with the paper of Haralambous would consider change of the quote mark in question believing that Org developers were not aware of the "right" symbol. A comment in the source code may provide a hint that the choice was conscious. I forgot to mention it in my message from 2020-08-15 that I did not find the U+201F character in TeX pre-unicode LG* encodings for Greek.
Re: [PATCH] Fix some typos
Please, forgive my ignorance of Shakespeare's poetry. On 17/09/2021 17:05, Marco Wahl wrote: >> On 17/09/2021 04:40, Stefan Kangas wrote: Please find attached another clean-up patch that fixes a small number of typos. > > Thou shall not change "memeory" to "memory" tho I think, a bit more is required to avoid recurring attempts to change spelling if you would like to see such variant. Static code analyzers usually have a feature that allows to ignore specific warning at a particular line, see e.g. https://flake8.pycqa.org/en/latest/user/violations.html#in-line-ignoring-errors for Python's flake8. Maybe "LocalWords:" could do a similar trick for ispell.el at least for the whole file. Unsure if it is possible to add an exception for the quote only. However there is namely "memory" in the "1609 Quarto", see e.g. https://en.wikipedia.org/wiki/Sonnet_1 Web pages with the same variant as in the Org manual do not mention the source (particular edition). I hope, I just do not know what is considered as the canonical variant for not so old language.
Re: toggle-truncate-lines outside table and source regions
How about adding (lambda () (toggle-truncate-lines 1)) to org-mode-hooks in your EMACS init file? -- Bill On Wed, Sep 22, 2021 at 2:59 AM Luca Ferrari wrote: > Hi all, > is it possible to instrument org-mode to automatically truncate lines > only on "regular" text, i.e., outside table and source regions? > I know why org-mode disables line truncation, but to me it is quite > annoying when dealing with long text lines. > > Thanks, > Luca > >
Re: [ANN] org-ql 0.6 released
Hi Adam, Thank you very much for this great package. I could no longer live without org-ql/helm-org-ql :-) Best regards, Juan Manuel Adam Porter writes: > Hi friends, > > FYI, I just released version 0.6 of org-ql. Please see the changelog > here: > > https://github.com/alphapapa/org-ql#06
Re: Bug: Fontify error with markdown source block [9.4.4 (release_9.4.4 @ /usr/share/emacs/28.0.50/lisp/org/)]
Just as a little bump/update. My current thoughts on this are that this is probably an issue with `markdown-mode', but it would be good if issues with langs’ modes used in Org src blocks weren’t able to mess with Org’s fontification, and so this patch[1] or one like it should be merged. All the best, Timothy Footnotes ─ [1] The comment message is still a placeholder as of this moment, but that’s easy enough to change
Re: Heading toward Org 9.5
Is there a page where I can see the changes when moving from 9.4 to 9.5. I am really exited about the upcoming version. I am sure there are lots of changes. Much more than what are mentioned at https://updates.orgmode.org/#changes -- Regards ~Pankaj
toggle-truncate-lines outside table and source regions
Hi all, is it possible to instrument org-mode to automatically truncate lines only on "regular" text, i.e., outside table and source regions? I know why org-mode disables line truncation, but to me it is quite annoying when dealing with long text lines. Thanks, Luca
[ANN] org-ql 0.6 released
Hi friends, FYI, I just released version 0.6 of org-ql. Please see the changelog here: https://github.com/alphapapa/org-ql#06 -- Thanks, Adam
