> Uwe Brauer writes:
> AFAIK, using "-" is hard-coded in org-toggle-item.
> Also, 1.1 is not a valid list bullet.
> So, you need to implement alternative bullet support yourself.
> Patches are welcome!
I see, several observations.
1. For headings there is a third party package called
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
org-latex-pdf-process says that
Its value is ("
Ihor Radchenko writes:
>>> I think this should be considered a bug, since the glyph used (LEFTWARDS
>>> TRIANGLE-HEADED ARROW / #2b60) is not present in most fonts.
If that is true (I don't know) then maybe we should just use a more
ubiquitous glyph?
> The commit is supposed to fall back to ASC
Daniel Ortmann writes:
> Ihor,
> What are your thoughts?
>
> On 7/12/22 15:03, Juan Manuel Macías wrote:
>> Juan Manuel Macías writes:
>>
>>> The most reasonable thing would be to use a more
>>> common symbol. But I'm still intrigued by the origin of that symbol...
>> It seems that the culprit is
Sharon Kimble writes:
> Can someone enlighten me as to why it isn't working? And how can I get them
> all working properly please?
Your appear to have "mixed" Org installation when part of Org is loaded
from built-in Org distribution and part is loaded from your downloaded
newer version.
Pleas
Ihor,
What are your thoughts?
On 7/12/22 15:03, Juan Manuel Macías wrote:
Juan Manuel Macías writes:
The most reasonable thing would be to use a more
common symbol. But I'm still intrigued by the origin of that symbol...
It seems that the culprit is in line 1592 of org-agenda.el
I think this
The attached patch fixes a small typo I found in the
`org-refile-targets' docstring.
From fe1c6f69ffcd3dfdb04c728f92e63e2fb1e4b4c0 Mon Sep 17 00:00:00 2001
From: Stefan Kangas
Date: Wed, 13 Jul 2022 00:22:20 +0200
Subject: [PATCH] ; * lisp/org-refile.el (org-refile-targets): Fix typo.
---
lisp/o
Fraga, Eric writes on Tue 12 Jul 2022 14:08:
> On Tuesday, 12 Jul 2022 at 14:53, alain.coch...@unistra.fr wrote:
> > So far so good. (Well almost: why does '#+RESULTS:' show 'bar' and
> > not 'foo'? After all, I'm just setting 'my-var', I'm not asking to
> > display its value. But that's
Juan Manuel Macías writes:
> The most reasonable thing would be to use a more
> common symbol. But I'm still intrigued by the origin of that symbol...
It seems that the culprit is in line 1592 of org-agenda.el
I think this should be considered a bug, since the glyph used (LEFTWARDS
TRIANGLE-HEAD
Hi, Daniel,
Daniel Ortmann writes:
> – Would using the ASCII '<' character be a better solution?
I've done a quick test and a few very popular (and more or less
complete) fonts don't include a glyph for the LEFTWARDS TRIANGLE-HEADED
ARROW #2b60 character: DejavuSans, Iosevka, Hack Source Code Pr
That odd new character just showed up after a normal daily org-mode 'git
pull'.
The Symbola.ttf font worked fine.
I used this page for for instructions.
https://linuxconfig.org/how-to-install-and-manage-fonts-on-linux
After copying the font to ~/.local/share/font/ and running the 'fc-cache
-vf
Hi,
Daniel Ortmann writes:
> Any clues where this particular symbol resides? A hint about the
> package name would wonderful. :-)
To be able to display "unusual" symbols in Emacs, I usually use the
symbola font:
You can download it here:
https://fontlibrary.org/en/font/symbola
And then:
(s
Hello,
During the past couple of weeks I have been seeing a new character in
the agenda when the log is on and I am displaying the time grid. I have
tried to find and install this character representation on Fedora-based
Linux but have not found the magic.
Any clues where this particular sym
Den tis 12 juli 2022 17:51Henrik Frisk skrev:
>
>
> Den tors 7 juli 2022 kl 12:48 skrev Ihor Radchenko :
>
>> Henrik Frisk writes:
>>
>> > Ihor Radchenko recently mentioned org-capture-ref and I decided to try
>> to
>> > use it, but I'm having trouble getting it to work. I have org-protocl
>> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Using this template culled from the org-mode manual
- --8<---cut here---start->8---
#+BEGIN_SRC emacs-lisp
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "~/.emacs.d/org/scratch.org" "Tasks"
Today I discovered that luaotfload included in v. 3.12 a new
experimental function, luaotfload.add_fallback, to be able to add a list
of fallback fonts to a LuaTeX document, at a low level.
(More info on page 18 of the luaotfload manual, with some examples).
I've been experimenting a bit with thi
Alain,
let's see. maybe look in the org manual for ":results" (with "value" or
"output" as options) and ":exports" (with "code" or "results" or "both"
as options).
that might help?
cheers, Greg
On Tuesday, 12 Jul 2022 at 14:53, alain.coch...@unistra.fr wrote:
> So far so good. (Well almost: why does '#+RESULTS:' show 'bar' and
> not 'foo'? After all, I'm just setting 'my-var', I'm not asking to
> display its value. But that's incidental.)
It's not incidental. By default, the results
Jack Kamm writes:
>> I cannot reproduce. Please, update your Org to the latest version, try
>> to reproduce, and provide the detailed steps required to obtain the
>> confusing behaviour you are seeing.
>
> I attach a couple files for a minimal reproducible example of both
> issues.
>
> Steps to r
Hi Ihor,
On Tue, 12 Jul 2022 at 10:46, Ihor Radchenko wrote:
Thanks for the detailed analysis!
I thank you again for your continued interest in this little report.
I dug through the old commits and found where this behaviour has been
introduced:
Commit 0bbf3a9bd message details the curren
Hello. The manual says:
Org evaluates code in the following circumstances:
_Source code blocks_
Org evaluates source code blocks in an Org file during export.
Org also evaluates a source code block with the ‘C-c C-c’ key
chord.
NB: each test below is performed with
On Tue, 12 Jul 2022 at 13:36, John Kitchin wrote:
> Maybe it is still needed so the tooltip looks nice.
currently, oc-basic.el contains the single activation (fontification)
processor (called "basic") shipped with Org, the other oc-*.el files
provide only export processors.
best wishes,
András
Maybe it is still needed so the tooltip looks nice.
On Tue, Jul 12, 2022 at 7:15 AM András Simonyi
wrote:
> Dear All,
>
> On Sun, 10 Jul 2022 at 09:17, Ihor Radchenko wrote:
>
> > AFAIU, oc-natbib/oc-bibtex also do not support @string because they also
> > rely upon the built-in Emacs parser fo
Stefan Nobis writes:
> Hmmm... maybe add optional extra config/output option to the fontset,
> like so:
>
> ┌
> │ ;; Fonts
> │ ((myfonta . ((pdflatex . "etc.") (lualatex ...) (html ...) ...))
> │ (myfontb ...)
> │ ...)
> │ ;; Fontsets
> │ ((myfontset .
> │ ((sans . myfonta)
> │(serif .
Dear All,
On Sun, 10 Jul 2022 at 09:17, Ihor Radchenko wrote:
> AFAIU, oc-natbib/oc-bibtex also do not support @string because they also
> rely upon the built-in Emacs parser for bib files.
> I have submitted a bug report to Emacs devs [1]. Hopefully it can be
> fixed on Emacs side without a ne
Dear All,
On Mon, 11 Jul 2022 at 04:05, Ihor Radchenko wrote:
> >> Then, I am wondering if parsebib can be added to ELPA or at least
> >> non-GNU ELPA. The same can be said for all other dependencies of
> >> citeproc.el and for citeproc itself.
> non-GNU ELPA is also fine. The idea is to avoid
Hi
As it was pointed out to me in
https://github.com/kjambunathan/org-mode-ox-odt/issues/94
It is possible to start with a ods file then convert it to csv with
formula to obtain something like this
#+begin_src
3,6,"=SUM($A1:$B1)"
1,3,"=SUM($A2:$B2)"
1,2,"=SUM($A3:$B3)"
#+end_src
That can be
Juan Manuel Macías writes:
> [1] I have to add, by the way, that MatchLowercase is not always a
> panacea.
Hmmm... maybe add optional extra config/output option to the fontset,
like so:
┌
│ ;; Fonts
│ ((myfonta . ((pdflatex . "etc.") (lualatex ...) (html ...) ...))
│ (myfontb ...)
│ ...)
28 matches
Mail list logo
