Hi Max,
Answers inline.
On Fri, 18 Apr 2025 at 19:05, Max Nikulin wrote:
> On 18/04/2025 15:13, Pedro Andres Aranda Gutierrez wrote:
> >
> > I think that trying to address all mappings out-of-the-box is not very
> > realistic and would add too much noise.
>
> Just necessary mappings (for specif
Hi folks,
I’m using Org mode, and org-num-mode seems to interfere with
org-column-mode’s appearance.
Recipe:
1. emacs -Q
2. C-x b test RET
3. M-x org-mode RET
4. M-x org-num-mode RET
5. Insert the contents between the lines in the buffer:
Hi all
It is often very comfortable for tables that possess hlines to use the
following syntax
#+Name: TODO
| | Name | Amount |
|---++|
| # | start | 23.97 |
| || 41.97 |
| || 46.06 |
| # | end| 32.00 |
|---++|
| || 436.69
On 18/04/2025 15:13, Pedro Andres Aranda Gutierrez wrote:
I think that trying to address all mappings out-of-the-box is not very
realistic and would add too much noise.
Just necessary mappings (for specific document) instead of all ones
should not be perceived as noise.
luaotfload.add_f
Hello,
Attached to this e-mail you could find a small patch for the HTML export
backend.
This patch add an in-file option for enabling headlines self link.
# Motivation
Until now, to add a self link on each headline in the HTML export, user
needed to set the variable `org-html-self-link-headli
On Thu, Apr 17 2025, Ihor Radchenko wrote:
> Leo Butler writes:
>
>>> Better https://elpa.nongnu.org/nongnu/cdlatex.html
>>
>> Take 2.
>> -from [[https://elpa.nongnu.org/][NonGNU ELPA]] with the
>> [[https://www.gnu.org/software/emacs/manual/html_node/emacs/Package-Installation.html][Emacs
>> pa
Hello Thomas,
thank you for your help.
On 2025-04-17, Thomas Ingram wrote:
> I think the easiest solution would be to use a :completion-function to rename
> all the filenames to remove the lang identifier.
>
> (defun my/rename-files (project-alist)
yes I was considering this but
>
>
>
Thank you.
I will use the mirror.
Ihor Radchenko writes:
> Sébastien Gendre writes:
>
>> I wanted to pull the latest commit of the branch main in the Org-mode
>> repository. On "https://git.savannah.gnu.org/git/emacs/org-mode.git";.
>>
>> And I got an error 502.
>>
>> This is the full Magit lo
with M-x org-export-dispatch, c (Export to
iCalendar), f (Current file) contains the event
BEGIN:VEVENT
UID:DS1-ddf9e720-3c8a-4b2a-93d8-62dde9cdf5a8
DTSTART;VALUE=DATE:20250418
EXDATE;VALUE=DATE:20250418
RRULE:FREQ=MONTHLY;BYDAY=1SA
SUMMARY:1st Sat/month
END:VEVENT
DSTART and EXDATE are set to
在 2025/4/16 11:24, Karthik Chikmagalur 写道:
After debugging, I found that it is because dvisvgm omitts the default
#000 color value when generating SVG file, and emacs has a unique way of
displaying the SVG, which caused foreground color to be applied to it.
Just a note: this has been addressed
Bastien Guerry writes:
> And I'm curious to see how it compares to other workflows.
My keywords are similar to yours, but slightly more readable:
- ONGO instead of STRT
- SKIP instead of CANX
:)
Rudy
--
"Logic is a science of the necessary laws of thought, without which no
employment of the
What about link integrity? With relative Org links, you'd need an export
filter for links as well, to remove the language infix and to add the
language directory, so links would match the location and names of the
targets. Unless you sacrifice the affordance of having working Org links
that expor
Hello,
Please is there a way to remove all the :base-extension of the sourge
file name in the exported file name?
For example when publishing a project to HTML I would like to get this
output file name:
index.en.org -> index.html
instead of
index.en.org -> index.en.html
Honestly I conside
Same in HTML export as Guillaume reports for ODT: A {{{title}}} macro in
DESCRIPTION and KEYWORDS keywords is unexpanded in the exported meta
tags.
However, macros in the text that reference those keywords, in turn, *do*
expand to the contents of those keywords *with* the title macro
expanded. I
The info node "(org) Code Evaluation Security" fails to mention
diary-style (%%) sexps at all. Furthermore, it appears that the
`org-diary-sexp-entry` function will readily evaluate any Lisp function;
it does not necessarily need to be related to dates or considered safe.
For example the following
And the file ;-)
/PA
On Fri, 18 Apr 2025 at 10:12, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:
> HI again
>
> I've attached an example .tex (lualatex) file, with bits and pieces from
> many discussions at tex.stackexchange and elsewhere.
> The structure would allow us to create two
HI again
I've attached an example .tex (lualatex) file, with bits and pieces from
many discussions at tex.stackexchange and elsewhere.
The structure would allow us to create two custom variables to generate the
code:
one for the direct lua fallback list and another for the \set...font
mappings
I
Hi Russell,
Russell Adams writes:
> In comparison, I often use a file per project and I focus more on TODO
> trees than scheduled items. I do maintain a few standard files that I
> only update via "remember", and access via agenda.
Thanks for sharing.
> Everyone finds their own workflow.
Yes,
18 matches
Mail list logo
