Ihor Radchenko writes:
> Hanno writes:
>
- after "a..z" runs out, '{', '|' and '}' are being used which seems
reasonable -- but after that, I get '\200' and similar before reaching
'©'...
>>>
>>>This is indeed true, but what can we do? There are only that many
>>>characters
>> P.D: Just when I was going to send this I tried to investigate it a
>> little bit more to not waste anyone's time, and I found the variable
>> 'org-agenda-skip-comment-trees', which defaults to 't'. So now I see that
>> if it is set to 'nil' it would not be inconsistent to me anymore, but I
> Ihor Radchenko writes:
> Colin Baxter writes:
>> > https://gitlab.com/maciaschain/org-verse-num
>>
>> Your site tells me to turn JavaScript, enable Cookies and
>> complete a CAPTCHA, all of which I refuse to do.
>>
>> Do you have an alternative web-site?
Hi Jeremie
In my emacs it works great. Even org-fragtog that allows you to edit in
an interactive manner.
- Just in case it could be helpfult, these are the lines in my init file
that I can find related to LaTeX:
(custom-set-variables
'(org-preview-latex-image-directory
Juan Manuel Macías writes:
> BTW, is there any proprietary JavaScript free alternative to
> GitLab/GitHub? I would be very grateful for any recommendations.
For self-hosted solutions, you may check out https://gitea.io/en-us/
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode
Hello Juan,
On Sunday, 7 Aug 2022 at 14:22, Juan Manuel Macías wrote:
> I've added some minor improvements to my little package 'org-verse-num',
> which was born out of necessity in my translation to spanish
> (work-in-progress) of Homer's Odyssey (11600 verses spread over 24
> books):
>
Colin Baxter writes:
> Your site tells me to turn JavaScript, enable Cookies and complete a
> CAPTCHA, all of which I refuse to do.
>
> Do you have an alternative web-site?
Sorry for the inconvenience. I plan to set up my own GitLab instance in
the future, but I don't have time to do it anytime
alain.coch...@unistra.fr writes:
> alain.coch...@unistra.fr writes on Sat 9 Jul 2022 08:10:
>
> > the examples I found on this mailing list did not work for me).
>
> I think I now understand why this was so: because latexmk was not
> installed on my system. In this case the docstring of
>
Colin Baxter writes:
> > https://gitlab.com/maciaschain/org-verse-num
>
> Your site tells me to turn JavaScript, enable Cookies and complete a
> CAPTCHA, all of which I refuse to do.
>
> Do you have an alternative web-site?
While I understand your frustration, please note that you really do
> Juan Manuel Macías writes:
> Hi all, I've added some minor improvements to my little package
> 'org-verse-num', which was born out of necessity in my translation
> to spanish (work-in-progress) of Homer's Odyssey (11600 verses
> spread over 24 books):
>
Hi all,
I've added some minor improvements to my little package 'org-verse-num',
which was born out of necessity in my translation to spanish
(work-in-progress) of Homer's Odyssey (11600 verses spread over 24
books):
https://gitlab.com/maciaschain/org-verse-num
org-verse-num includes some
Ypo writes:
> When turning headlines into plain lists ~(org-ctrl-c-minus)~, I think
> footnotes should be moved to the bottom of the main headline.
>
> Example; Original headlines:
>
> * Main headline
> ** Headline 1
> [fn:1]
>
> [fn:1]
> * Headline 2
>
>
> ~C-c -~
Hi, Uwe,
Three ideas:
1. Since your solution depends on the row number (@#) in any case, your
use case does not actually depend on hline-relative references, does
it? Then you can also assign to absolute row numbers, either by
- assigning to the range rather than to the colum, which
Jack Kamm writes:
> I found that Org entries containing markdown source blocks don't get
> properly folded on the main development branch, when markdown-mode is
> also loaded.
>
> To reproduce:
>
> 1. Download markdown-mode from MELPA or Github. [1]
> 2. Fix the paths in the attached init.el.
>
András Simonyi writes:
> the attached patch adds support for three new citation styles which
> recently got supported by citeproc-el:
>
> - cite/title or cite/ti to cite only the title of an item,
> - cite/locators or cite/l to cite only the locators, and
> - cite/bibentry or cite/b to cite the
Ihor Radchenko writes:
> Thanks for the heads-up!
> Comment blocks are not supposed to contain Org markup, and thus it indeed
> makes sense to support them in org-edit-special and in structure
> templates.
>
> See the attached patch.
Applied onto main via a303a794f.
Ihor Radchenko writes:
> Marcin Borkowski writes:
>
>> When I try to edit a property in column view, I get the following error
>> message:
>>
>> Invalid column specification format: nil
>>
>> This only seems to happen if the point is not too close to the left
>> margin. I did a bit of digging
Hello Jack,
Thanks for reporting. I can reproduce the bug.
Best regards,
Jeremie
On Saturday, 6 Aug 2022 at 14:10, Jack Kamm wrote:
> Hello,
>
> I found that Org entries containing markdown source blocks don't get
> properly folded on the main development branch, when markdown-mode is
>
18 matches
Mail list logo
