Dear list,
This is my problem: I have a large set of org files (created with
org-roam), which contains all my thoughts on different topics (for
example "work1", "work2", "personal1"...)
I would like to create different projects (for example "work1",
"work2", "personal1") to be able to publish
I am not seeing the problem anymore after installing the Symbola fonts.
On 7/16/22 04:15, Ihor Radchenko wrote:
Daniel Ortmann writes:
More information on that character:
position: 195 of 690 (28%), column: 26
character: ⭠ (displayed as ⭠) (codepoint 11104,
Uwe Brauer writes:
> Now if I want to switch to the convention used in Germany (that might be
> relevant if I want to export it later to csv, but this is a different
> topic) does work in a strange way, any comments? [...]
Hi, Uwe,
If you only need to export to LaTeX you can load the siunitx
"M. Pger" writes:
> Thank you for your answer. Here it is:
>
> 1. Create the following directory structure (3 directories):
> ~/test/
> ├── content
> ├── html
> └── .packages
>
> 2. Create the .el script to build the website (=~/test/build.el=):
>
> #+begin_src elisp
> ;; * Set the package
Kevin,
> On Jul 17, 2022, at 1:54 PM, kevinbanjo wrote:
>
> When I look at the doc string for (org-macro-replace-all) it says:
>
> Optional argument KEYWORDS, when non-nil is a list of keywords,
> as strings, where macro expansion is allowed.
>
> I tried passing it '("export-block") but it
Thanks for your suggestion. I added the following:
#+begin_src elisp :eval no :exports code
(setq my-var "org mailing list")
(message "Hello, %s" my-var)
#+end_src
When exported with ~C-c C-e h o~, syntax highlighting is implemented (with
colors). When exported with org-publish
Valentin Lab writes:
>> Also, I am not sure if we really need a new custom variable. We already
>> have many. What about simply allowing an integer value of
>> org-adapt-indentation?
>>
>
> Well, my guess was that the "adapt" word in `org-adapt-indentation' was
> referring to adaptive (in
Hugo,
I am sorry if I am wrong, but I do not see you among known Org
contributors. You patch is likely greater than it is allowed for
TINYCHANGE, so before you patch can be committed, copyright assignment
should be signed, see
https://orgmode.org/worg/org-contribute.html#copyright for
Ihor Radchenko writes:
> Do you refer to the paragraph below when saying that Org implementation
> makes it hard to add new features? The rest of the above paragraph
> implies that the difficulty is on LaTeX side, not on Org side.
Sorry for not explaining clearly. Actually I think the problem is
Hi Ihor,
On Mon, 18 Jul 2022 at 14:28, Ihor Radchenko wrote:
I feel that you are overcomplicating things a bit.
Well, the most important objective of the analysis was to try to figure
out if the `todayp' condition was too strict or not. Since your
suggested fix implies removing it as
Valentin Lab writes:
>>> @@ -1216,6 +1259,13 @@
>>> (org-test-with-temp-text "* H\n:PROPERTIES:\n:key:\n:END:"
>>> (org-indent-region (point-min) (point-max))
>>> (buffer-string)
>>> + ;; ;; Indent property drawers according to
Juan Manuel Macías writes:
> latex-lang: babel(sorbian) variant(upper)
> provide(hebrew:import,hyphenrules=+) options(bidi=default),
> others(french,catalan)
>
> returns:
>
> \usepackage[french,catalan,uppersorbian,bidi=default]{babel}
> \babelprovide[import,hyphenrules=+]{hebrew}
PS: In
this page:
https://orgmode.org/manual/Macro-Replacement.html#index-macro-replacement_002c-during-export
says:
Org also recognizes macro references in keywords, such as ‘CAPTION’, ‘TITLE’,
‘AUTHOR’, ‘DATE’, *and for some back-end specific export options.*
How do I discover what those back end
Hello,
I decided to write an Org backend to Haddock[1], so that haskell library
documentation can be generated in org mode markup. Compared to the
existing backends (html, latex and hoogle), the org format allows
utilising features like the infinite levels of heading hierarchy,
flexible folding
Hi Ihor,
> ...
> Note that you are using %^G, while implies (see org-capture-templates
> docstring):
>
> %^G Prompt for tags, with completion on all tags in all agenda files.
^
Thank you so much for the help.
On 17/07/2022 15:58, Ihor Radchenko wrote:
Juan Manuel Macías writes:
I think LEFTWARDS ARROW / #2190 of the 'arrows' Unicode block is much
more common:
Thanks for testing!
I now changed org-agenda to use LEFTWARDS ARROW in b4a72ddf9.
This does not completely solve the reported problem but
On 18/07/2022 17:32, Juan Manuel Macías wrote:
For example, something like this:
latex-lang: babel(sorbian) variant(upper) provide(hebrew:import,hyphenrules=+)
options(bidi=default), others(french,catalan)
returns:
\usepackage[french,catalan,uppersorbian,bidi=default]{babel}
Max Nikulin writes:
> On 18/07/2022 17:32, Juan Manuel Macías wrote:
>> For example, something like this:
>> latex-lang: babel(sorbian) variant(upper)
>> provide(hebrew:import,hyphenrules=+) options(bidi=default),
>> others(french,catalan)
>> returns:
>>
Dear org community,
I have also faced the problem and have made a patch to fix it. This patch would
not be the best solution since I'm unfamiliar with Emacs Lisp and the detailed
implementation of org-mode. I'd appreciate that if you would review and merge
the patch attached to this mail.
Kind
Hi Ihor,
I'm mostly AFK this week so I won't be able to investigate, I remember
this area was fragile.
Feel free to push the fix if it seems right to you. We can revert it
back or improve it if needed.
Thanks a lot!
--
Bastien
Dear Bastien and org community,
I have also faced the problem and have made a patch to fix it. This
patch would not be the best solution since I'm unfamiliar with Emacs
Lisp and the detailed implementation of org-mode. I'd appreciate that if
you would review and merge the patch attached to
Hi
In my current setting, the following works
| 3.5 | 4.2 | 7.7 |
#+TBLFM: $3=$1+$2
Now if I want to switch to the convention used in Germany (that might be
relevant if I want to export it later to csv, but this is a different
topic) does work in a strange way, any comments? I would expect
Ypo writes:
> It works! Thanks, Ihor.
>
> How could I've known? Should I've known?
The manual on diary integration (11.3.1 Weekly/daily agenda) says:
If you are using the diary only for expression entries and holidays,
it is faster to not use the above setting, but instead to copy or even
It works! Thanks, Ihor.
How could I've known? Should I've known?
El 18/07/2022 a las 1:49, Ihor Radchenko escribió:
Ypo writes:
I am starting to use org-contacts and wanted to unify my existing
"Birthdays" list, with the new formatted contacts I am creating.
Do the anniversaries have to
Gustavo Barros writes:
> ... (lots of detailed analysis with various cases)
> WDYT?
I feel that you are overcomplicating things a bit.
What if we simply change all the agenda lines if and only if their date
in agenda is earlier or equal to the next scheduled time (after repeater
is triggered)?
Juan Manuel Macías writes:
>> For Max's comment, using plist/alist would make things more clear
>> code-wise for future developers. I always find it annoying when I need
>> to go back and forth checking which element should be second or third or
>> forth in the list. Especially if the variable
Den mån 18 juli 2022 kl 01:56 skrev Ihor Radchenko :
> Henrik Frisk writes:
>
> >> Could you please provide a bit more details on what you did, what you
> >> expected to get, and what you got?
> >>
> >> Yes, of course!
> >
> > I saw in another thread recently that you had the bibtex captured as
Thank you for your answer. Here it is:
1. Create the following directory structure (3 directories):
~/test/
├── content
├── html
└── .packages
2. Create the .el script to build the website (=~/test/build.el=):
#+begin_src elisp
;; * Set the package installation directory (in order not to
28 matches
Mail list logo
