Hi All,
This is just some tweaks to the styling in ox-html that I think may
appeal (and prevent ridiculously long lines on non-small displays, which
are an issue for legibility).
I also took the opportunity to remove the (obsolete) CDATA strings and
make the CSS more consistently formatted. If yo
Gah! I left the subject as a placeholder [shame emoji].
Apologies for that.
Why do I always seem to notice these things as the Email is sending...
--
Timothy
TEC writes:
> Hi All,
>
> This is just some tweaks to the styling in ox-html that I think may
> appeal (and prevent ridiculously long
Yeah, I also found that confusing. Basically, because both mean the
same.
I think that a better description for those variables would be
+ =org-id-locations=: List obtained from `org-id-locations-file'. This
list maps each ID to the file in which the definition occurs. It
contains lists of the
This is helpful clarification, thank you. But does that mean that, if I
change the directory where some files with UUIDs are located, there's no
way to programmatically make sure that Org can find those IDs again (since
there's no way to simply add a folder, rather than a list of files, to
=org-id-
Ihor Radchenko writes:
> > Is there a way to get only the :LAST_REPEAT: prop logged, without the
> > ever-growing list?
>
> I guess you can try to play with org-log-done and org-log-repeat
> variables.
Thanks. But as far as I recall, that's what I already tried and it
didn't help.
As far as I
Michael Heerdegen writes:
> As far as I understand, the logging is implemented in
> `org-auto-repeat-maybe', and the thing I do not want is caused by the
> `org-add-log-setup' call, and that is done unconditionally unless
> `org-log-repeat's value is nil. Which I don't want because this would
>
Ihor Radchenko writes:
> You are right. Since this is hard-coded, you may have to use :around
> advice to disable org-log-setup: [...]
Do you think others may want the same and it could be worth to implement
this feature?
Michael.
Looking into the code related to 'pty problem with
start-process-shell-command, I have realized that the following case is
not handled correctly:
#+begin_src elisp
(setq org-file-apps '(("\\.pdf::\\([0-9]+\\)\\'" . "xpdf %s %1")))
#+end_src
I hope, I adapted an example from [[help:org-file-a
On 20/01/2021 10:21, Christopher Miles wrote:
Thanks for your working. I will modify my mailcap config temporary until Org
Mode fix this issue. You're right, this change might break some behavior of some
users. I don't understand Emacs sub-process mechanism. Can't help on this
problem. But I'm i
On Tue, Jan 19, 2021 at 08:45:22PM +0100, mitch--- via General discussions
about Org-mode. wrote:
> I have created a minimal test using the ox-ascii backend that shows
> the same behaviour in Org core.
Which is attached here because it forget it in the original mail.
Sorry
Christian
PS: My "Fr
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
---
Maxim Nikulin writes:
> I have realized that :filter argument is not appropriate to arbitrary
> handler that could spam with various assert messages. Maybe :sentinel is
> better to report configuration problem to user when handler is called
> with inappropriate arguments.
Yes, use ~:sentinel
Michael Heerdegen writes:
> Do you think others may want the same and it could be worth to implement
> this feature?
It should be not too hard to implement. For example, one can add another
possible value of org-log-repeat. Patches welcome ;)
Best,
Ihor
Guillaume MULLER writes:
> This is a simple enhancement proposition for C-c C-l (insert link): when
> user starts the link with ./ or / or file: , it would be great if org-mode
> could
> propose completions based on some local-files listing (dired?)
org-mode does it already. Try C-c C-l file:
TEC writes:
> TEC writes:
>
> Sorry about that, here's an actual revision.
Thanks, this series is a good improvement as far as I can tell. And
thank you Jens for all of the careful reviews.
I've applied this (a8df7670c) with two minor changes (shown in the diff
at end): s/with with/with/ in a
Tim Visher writes:
> Nice! I don't know enough about `org-export` but FWIW the use case I have
> is not to have an explicit `title` property but instead just the default
> title of the heading contents. I assume that's all handled transparently by
> the `(plist-get …` section.
>
> Do you have any
Kyle Meyer writes:
> I've applied this (a8df7670c) with two minor changes (shown in the diff
> at end): s/with with/with/ in a docstring and move an element to its own
> line to avoid the warning from lisp-mode's lisp--match-hidden-arg.
Thanks :)
> This thread has gone on long enough that I'l
17 matches
Mail list logo
