Detlev Zundel writes:
> Hi orgmode-list!
>
> I currently have a problem while exporting org-babel blocks to html or
> latex output. Even though I explicitely specify ':exports result' for
> the blocks, the exported document contains both the (syntax colored)
> code block and the code. I noticed
Hi
The following drives me a bit crazy.
I have two functions, one for email.
(defun my-color-red-html ()
(interactive)
(while (re-search-forward "#\\([^#]*\\)#" nil t)
(replace-match "\\1")))
I put this function into two hooks
(add-hook 'org-mime-html-hook 'my-color-red-html)
(
Uwe Brauer writes:
..
> (add-to-list 'org-export-filter-plain-text-functions 'my-html-red)
..
> But if I have
> #<2023-02-11>#
> in an org file and export it to html, no color is added to the timestamp.
>
> I don't know how to debug this.
>
> Any idea?
In org, "<2023-02-11>" is a date, not
>>> "BB" == Bruno Barbier writes:
> Uwe Brauer writes:
> ..
>> (add-to-list 'org-export-filter-plain-text-functions 'my-html-red)
> ..
>> But if I have
>> #<2023-02-11>#
>> in an org file and export it to html, no color is added to the timestamp.
>>
>> I don't know how to debug this.
>>
>>
Uwe Brauer writes:
>> #+MACRO: IDATE @@html:$1@@
>
>> {{{IDATE(<2023-02-11>)}}}
> ...
> * Title {{{<2023-02-11>}}}
> {{{(<2023-02-11>)}}}
>
>
> Does not work when exporting to html, and I have recent developer org
> version installed
You forgot to specify IDATE macro name.
--
Ihor Radchenko //
Uwe Brauer writes:
"BB" == Bruno Barbier writes:
>
>> Uwe Brauer writes:
>> ..
>
>>> (add-to-list 'org-export-filter-plain-text-functions 'my-html-red)
>> ..
>
>>> But if I have
>>> #<2023-02-11>#
>>> in an org file and export it to html, no color is added to the timestamp.
>>>
>>> I don
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> #+MACRO: IDATE @@html:$1@@
>>
>>> {{{IDATE(<2023-02-11>)}}}
>> ...
>> * Title {{{<2023-02-11>}}}
>> {{{(<2023-02-11>)}}}
>>
>>
>> Does not work when exporting to html, and I have recent developer org
>> version installed
> You forgo
Uwe Brauer writes:
> <2023-02-11>
>
> But I would like to having the same result org-mime obtains
>
> Namely
>
> class="timestamp"> 11.02.2023
>
> Any chance to get that also?
#+MACRO: IDATE @@html:@@$1@@html:@@
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode
ch.emacs--- via "General discussions about Org-mode."
writes:
> When exporting a document to LaTeX with smart quotes enabled, I found
> that this had been ignored (e.g. "hello" vs ``hello'' in the output). I
> had the document language set to en-gb, which it seems disables smart
> quotes, as t
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> <2023-02-11>
>>
>> But I would like to having the same result org-mime obtains
>>
>> Namely
>>
>> 11.02.2023
>>
>> Any chance to get that also?
> #+MACRO: IDATE @@html:@@$1@@html:@@
Thanks but
,
Timothy writes:
> “export features” allow for the specification of qualities of the org buffer
> being exported that imply certain “features”, and how those features may be
> implemented in a particular export.
>
> This is done by augmenting the backend struct with two new fields:
> `feature-cond
On 09/02/2023 03:40, Leo Butler wrote:
On Wed, Feb 08 2023, Max Nikulin wrote:
I am curious if it is possible to avoid duplication by e.g. using noweb.
... I am not aware of how to
remove that duplication--all the examples I have found in the worg
source do what I have done above.
I have tri
Uwe Brauer writes:
> | #+MACRO: IDATE @@html:@@$1@@html:@@
> |
> | * Title <{{{IDATE(2023-02-11)}}}> o {{{IDATE(<2023-02-11>)}}}
> |
> | Will this work?
> | {{{IDATE(<2023-02-11>)}}}
> `
>
> Does not work for me
It does work. It's just that default css style for timestamps sets the
color
Matt writes:
> It seems to me like 02-ob-shell-async-non-file.patch is all that's needed for
> basic async in ob-shell. I'm able to run long processes like `guix pull' and
> `guix package -u' calls without issue and the results look like I expect.
> Similarly for running a web server, such a
Kevin Brubeck Unhammer writes:
More things also require translation in `org-export-dictionary'.
>
> The missing Norwegian Nynorsk "nn" org-export-dictionary entries:
Thanks!
Applied, onto main. On your behalf.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=bd34cb3f9
--
Ih
Kevin Brubeck Unhammer writes:
>> (defcustom org-clock-clocktable-language-setup
>> Contributions for other languages are also welcome.
>
> Here's Norwegian Nynorsk:
>
> (setq org-clock-clocktable-language-setup
> '(
>
> ("nn" "Fil" "N" "Tidspunkt" "Overskrift" "Tid" "AL
Max Nikulin writes:
>> Maybe better add this to "A.3 Adding Hyperlink Types" section of the manual?
>
> If you you believe that the (info "(org) Adding Hyperlink Types")
> section should be expanded then a complete example is necessary, some
> ideas may be picked from
>
> https://orgmode.org/wo
[ Adding Org ML back to CC ]
Uwe Brauer writes:
>>> | Will this work?
>>> | {{{IDATE(<2023-02-11>)}}}
>>> `
>>>
>>> Does not work for me
>>
>> It does work. It's just that default css style for timestamps sets the
>> color of its own.
>
> Well but then what should I do on a practical leve
> [ Adding Org ML back to CC ]
> Uwe Brauer writes:
> See "13.9.12 CSS support" section of Org manual.
Thanks!
#+OPTIONS: html-style:nil
Works, maybe is too blunt, but good enough for me
--
Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression ag
Bruno Barbier writes:
> Arthur Miller writes:
>
>>> Bruno Barbier writes:
>>> If you really want to just get the piece of text, you might be able to
>>> use the hook `org-capture-mode-hook' to replace the key binding to
>>> 'C-c C-c' in the capture buffer, so that it calls your own function tha
Arthur Miller writes:
> Based on a Reddit thread:
>
> https://www.reddit.com/r/emacs/comments/10xhvd8/a_little_readstring_utility_using_an_org_mode/j7xziao/?context=3
>
> I did a small experiment to see if I can re-use org-capture, to just capture a
> string from a buffer, without actually writin
often we include content in export templates that is only
relevant in
particular situations.
“export features” allow for the specification of qualities of
the org buffer
being exported that imply certain “features”, and how those
features may be
implemented in a particular export.
now `\
Ihor Radchenko writes on Fri 10 Feb 2023 09:56:
> Only a handful of interactive commands support invisible edit
> checks. In particular: self-insert-command (typing), deleting char
> forward/backward, and `org-meta-return'.
>
> I guess we may instead provide a defcustom and hook the check in
Hi,
I’m trying to use todo dependencies. I created the following tree, and set the
variable to `t` by evaluating the setq expression. But nothing changes. I can
use S- to cycle the TODO state of “Test Project" (none - TODO - DONE)
even though the children items are not DONE. Is that expected?
Robert Nikander writes:
> I’m trying to use todo dependencies. I created the following tree, and set
> the variable to `t` by evaluating the setq expression. But nothing changes. I
> can use S- to cycle the TODO state of “Test Project" (none - TODO -
> DONE) even though the children items are
alain.coch...@unistra.fr writes:
> At any rate, shouldn't "2.2.3 Catching invisible edits" be a little
> bit more specific about what kind of invisible edits are concerned?
> Or perhaps just a warning that it is not all of them.
We can indeed at such warning, but it will probably be not very help
Hi Bruno,
[...]
> Maybe:
>
>:exports result
> =>
>:exports results
>
> ?
Yes, indeed - you are 100% right. Looking at it so long, I was blind.
It was good writing things down as I found my mistake soon after sending
my initial mail ;)
https://lists.gnu.org/archive/html/emacs-orgmode/20
Arthur Miller writes:
> Bruno Barbier writes:
>
>> Arthur Miller writes:
>>
>> The hook `org-capture-mode-hook' will be run in your special
>> capture buffer. You can override the "C-c C-c" binding only there.
>
> Yes and in every other capture buffer
No. If you modify the hook only during you
Ihor Radchenko writes on Sat 11 Feb 2023 18:22:
> We can indeed at such warning, but it will probably be not very
> helpful.
I don't understand this. And isn't it better to have a more accurate
manual anyway?
Apart from that, since the default value in 9.6 is 'smart' ('nil' in
9.5), I wonder
Hi,
Ihor wrote:
>> Timothy writes:
>>
>> “export features” allow for the specification of qualities of the org
buffer
>> being exported that imply certain “features”, and how those features may
be
>> implemented in a particular export.
Looks like a cool "feature" that would bring some structure
Bruno Barbier writes:
> Arthur Miller writes:
>
>> Bruno Barbier writes:
>>
>>> Arthur Miller writes:
>>>
>>> The hook `org-capture-mode-hook' will be run in your special
>>> capture buffer. You can override the "C-c C-c" binding only there.
>>
>> Yes and in every other capture buffer
>
> No.
31 matches
Mail list logo
