Guillaume MULLER writes:
> - Would be great to be able to set this parameter per org buffer/file, e.g.
> with a #+ (#+OPTIONS?) command. Indeed, using the defaults is OK most of the
> time for most of the users. I only need this trick when I want to force
> lstlistings, and I only need to forc
"Tom Alexander" writes:
> Emacs version: 29.1
> Org-mode version: 163bafb43dcc2bc94a2c7ccaa77d3d1dd488f1af
>
> Found a conflict between the documentation and the parser behavior. The
> org-mode documentation[1] for description list items says that TAG '[...]
> does not contain the substring " :
Juan Manuel Macías writes:
> I think that with this patch the possible regressions are removed. I
> took the opportunity to add some improvements (the :babel-ini-alt,
> :script and :script-tag properties) and correct some errors and typos.
>
> I don't know if it's a valid path to allow the car of
Eduardo Suarez-Santana writes:
>> Or do you mean that you sometimes want to kill the target org buffer and
>> sometimes not?
>
> Yes, I mean that I sometimes want to kill the target org buffer and sometimes
> not. I don't want to kill the target buffer as the default behavior of my
> capture temp
Ihor Radchenko writes:
>> I don't know if it's a valid path to allow the car of each element to
>> also be a list of languages codes, but I couldn't think of a better
>> solution for the "de"/"de-de" cases. A similar case is in Chinese
>> Simplified (new language added), where the possible languag
Juan Manuel Macías writes:
>> I am not sure if making a breaking change to public constant is the best
>> approach.
>> What about simply adding an extra entry:
>> ("de" )
>> ("de-de" )
>> ?
>
> At first I had done it with extra entries, but I was wondering if there
> wasn't a more "economical
Hello everyone and thank you yantar for the response,
I did just that:
I have added a Polish translation for everything that I could find and
corrected one existing one.
I have also attached the diff file to this message.
Is that alright?
--- Original Message ---
On Friday, September 8
On Sat, Sep 09, 2023 at 09:18:27AM +, Ihor Radchenko wrote:
> For personal use-case, you can utilize
> `org-capture-after-finalize-hook', checking `current-prefix-arg' and
> killing the target org buffer according to the prefix argument passed.
> Then, for example, you can make C-u C-u C-c C-c
Dear all,
does someone here produce audio via Text-To-Speech (TTS) from Org
sources? I plan to do that in the context of emacs-reveal to
generate voice-over for reveal.js presentations, with open questions
[1] concerning my initial, experimental approach.
Currently, I like the default model of C
When compiling Org, I get the following warning:
In org--get-expected-indentation:
org.el:19192:8: Warning: Useless clause following default ‘cond’
clause
I looked at the source and confirmed it is not a false positive.
The following code is unreachable due to the (t ...) cond clause
before
I've turned OrgMode files into audio desktops
It was pretty simple
Just find the code that reveals what an icon is when you hover over it &
pipe it to some text-to-speech engine & then on to usual routes
On Sat, Sep 9, 2023 at 2:06 PM Jens Lechtenboerger <
lech...@wi.uni-muenster.de> wrote:
> D
Hi. I am on Gentoo. I wrote the following Elisp function:
--8<---cut here---start->8---
(defun J-org-icalendar-agenda-no-babel (&optional async)
"Invoke `org-icalendar-combine-agenda-files' without babel, maybe ASYNC.
Also, make broken Org links just get ma
Ihor Radchenko writes:
> I am thinking about something like
>
> (let ((de-plist '(...)))
> `(...
>("de" ,@de-plist)
>("de-de" ,@de-plist)
>...))
>
> This is copy-paste-proof and does not require breaking changes in the
> value structure.
I like the idea because it avoids errors, but
> The last meetup [1] turned out quite successful. Let's continue.
>
> [1] https://list.orgmode.org/877cq38gdt.fsf@localhost/ (meetup notes)
Thanks a lot for the notes, Ihor! I hope that I do not miss the next
meetup.
On 1/13/19 5:34 PM, Berry, Charles wrote:
Looks like your original idea to revise `org-export-data' might be best.
IIUC, you need to add the link text to the SIGNAL-DATA in each of the places
where `org-export-resolve-*-link' functions call `signal', then modify
`org-export-data' to ignore th
On 09/09/2023 16:06, Ihor Radchenko wrote:
Everything after the bullet and before the last " :: " is considered as
tag. Everything after the last " :: " is description.
I have not realized that besides
-
that is parsed as 'b">' description, another surprise is
- or ::
where descriptio
On 05/09/2023 16:42, Ihor Radchenko wrote:
Max Nikulin writes:
From my point of view it will be more sane behavior. However it may
require update of 3rd party ox backends.
Yes. The main problem is that I fail to understand the motivation behind
the current behaviour. git logs reveal that th
17 matches
Mail list logo
