I've been using a package called org-brain that is using, I'm all but
certain, the org-id-locations file as its database to store graph-like
relationships between org files and org headings. org-brain is a sort of
graph database which adds a PROPERTIES drawer with just the ID field with a
UUID to a
Hello,
I have some problems to manage my tasks for school with Org-mode. I had
read manual, blog posts and tried different way. With no success.
* What I need.
For the school, I have a list of projects to do. Each with a deadline
and different level of importance. And each project have their ho
Hi Ihor,
Ihor Radchenko writes:
> Xiyue Deng writes:
>
>> (This was first reported to Emacs at
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=69483)
>>
>> "mu4e"[1] (a popular Emacs mail client) uses Org to generate its
>> manpages. However, the generated output contains macros that are not
Hi Pedro Andres,
[...]
> Just for the record. The root cause for this problem is a :color definition
> with is not a string.
> So find the offending face definition and make sure the :color is a string,
Thanks for that useful tip which helped me to find the problem. Indeed
I was still using org
Max Nikulin writes:
> Your example uses a closed list of backends while "not (html or
> latex)" may be applicable to ascii, rst, some wiki dialects, etc.
Makes sense.
> Backend-specific markup may be more complex and content of fallback
> option may be different from text used in export snippets
On Mon, 11 Mar 2024 06:12:47 +0100 Aaron L. Zeng wrote ---
> * lisp/ob-shell.el (org-babel-shell-initialize): Override
> explicit-shell-file-name in addition to shell-file-name.
>
> When a session with shell source blocks, execution calls `shell',
> which checks `explicit-shell-fil
Hi,
> Message: 15
> Date: Mon, 11 Mar 2024 13:53:38 +0100
> From: Detlev Zundel
> To: emacs-orgmode@gnu.org
> Subject: Re: Strange behaviour detected today
> Message-ID: <87bk7l53ql@member.fsf.org>
> Content-Type: text/plain; charset=utf-8
>
> Hi,
>
> > Thanks a ton. I could bisect the issue
On 11/03/2024 20:59, Juan Manuel Macías wrote:
I have a bit different expectations in respect to export predicates.
It should be possible to express that some content should be exported
by all backend except the given list. The use case is fallback for
backends not covered by export snippets:
Dear Christian and Juan,
Thank you very much for your contributions. These are great and exactly
what I want. I'll probably go with an export filter.
Thank you
Best Wishes,
Colin Baxter.
Max Nikulin writes:
> On 10/03/2024 09:08, Juan Manuel Macías wrote:
>> I'm thinking about adding a new global attribute, `:export', that
>> would granularly control whether or not to export the object and how to
>> export it.
>
> I have a bit different expectations in respect to export predicates
Hi,
> Thanks a ton. I could bisect the issue and filed a bug yesterday. It
> seems to be the same commit that broke the themes.
May I ask what the outcome of all this was? I am now seeing the same
problem with Emacs from master as of today and wonder about the best way
to solve this in the short
When you display a list of tasks in Org-agenda, you have these columns:
- Category
- Status
- Task title
- Tags
But what I need in my list of work for school is:
- Task title
- Importance
- Deadline date and time
- Name of the work
Malik writes:
> Hello,
>
> I am also thinking about a good o
Hello,
I am also thinking about a good org-agenda configuration.
Your usecase sounds good.
What do you mean about the fixed columns and about what issues are you thinking?
Am 10. März 2024 08:54:45 MEZ schrieb "Sébastien Gendre" :
>Hello,
>
>I want to use Org-mode to track the works I have to do
Hi,
The footnote definitions are easy to fix with CSS since they are wrapped
in divs with the .footdef class.
#+begin_src css
.footdef sup { vertical-align: baseline; font-size: 100%; }
#+end_src
But as you point out, the footnote references, are not as
straigthforward given the structure --
Colin Baxter writes:
> Perhaps it's not possible because I see that .footref in css support is
> always .
You can modify a little so that it does not alter the paragraph
line spacing so much. In this example, with a value of 0em, it is
positioned on the baseline:
#+HTML_HEAD: sup {vertical-ali
Hi,
I am trying to create a list where the ordered list numbering expands
across sub-headings:
* Bacteria
** Acetobacter Species
1. Acetobacter aceti
2. Acetobacter rasens
* Fungi
** Candida Species
3. Candida famata
4. Candida firmetaria
* Others Unidentified Species
5. Escherichia species
6.
On 10/03/2024 09:08, Juan Manuel Macías wrote:
I'm thinking about adding a new global attribute, `:export', that
would granularly control whether or not to export the object and how to
export it.
I have a bit different expectations in respect to export predicates. It
should be possible to expr
Hi Antonio,
Antonio Romano writes:
[...]
> The :todo-keyword contains data about face and properties which are
> only relevant for viewing the document in the buffer and not for the
> .org file content itself. How can I read its text without any property
> info attached to it?
You could remov
Perhaps it's not possible because I see that .footref in css support is
always .
I use footnotes as [fn:1], etc. in an org-mode file which I then export
to html. In the output, I see the footnotes raised slightly above the
line. I do not want this. Instead, I would like the footnotes to be on
the line. Is this possible?
I have read the doc strings associated with the variabl
HI,
nothing like sleeping over a problem. This solution seems to be easier...
/PA
On Sun, 10 Mar 2024 at 12:49, Pedro A. Aranda wrote:
> Hi,
>
> I have been experiencing some inconsistencies with org-mode, which I
> have been able to trace own to using native compilation and not knowing
> wher
21 matches
Mail list logo
