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.
"Rick Lupton" writes:
>> #+attr_html: :height 300
>> [[file:image.png]] has a height of 300, but what if we want a
>> different height in @@[:html-height 300]{[[file:another-image.png]]}?
>>
>> Note how @@{...} markup assigns attributes to objects inside - the
>>
Ihor Radchenko writes:
> I have improved your patches a little, fixing the regular expression
> used to match headings ("^*" is not accurate, you need
> org-outline-regexp-bol), and adding another test case.
> See the attached.
Ah I see the difference, good catch. Thank you for the
Thanks for taking the time to comment thoroughly on this which seems generally
like it would be a good improvement.
On Tue, 9 Apr 2024, at 9:52 AM, Ihor Radchenko wrote:
> 2. Allow attaching auxiliary attributes to the on object level, as an
>equivalent of affiliated keywords on element
Rens Oliemans writes:
> * lisp/org-capture.el (org-capture-place-entry): Prepend heading to
> template if the template does not yet start with a heading.
>
> * testing/lisp/test-org-capture.el (test-org-capture/entry): Add two
> tests: no error is raised when org-capture is called with a
Christian Barthel writes:
> On the other hand: There are ways to specify the
> ordering like org-reverse-note-order. Would it make
> sense to have one global `org-reverse-order' that is
> dealing with reversing "everything" that is somehow
> dependent on ordering?
The problem is that it is not
Björn Bidar writes:
>> Fixed, on main. Alongside with other similar places.
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=78e9dd0c4
>
> I noticed after the change that captured links are not picked up.
>
> E.g.:
> 1. I capture a link using org-protocol
> 2. Switch to the
Ihor Radchenko writes:
> So, in the message I linked, Nicolas (the major Org mode contributor)
> was not right. I hence need to fix the parser and update Org syntax
> page. This includes fixing `org-element-clock-line-re' to account for
> CLOCK: => 1:00 syntax.
I changed the parser on main.
* lisp/org-capture.el (org-capture-place-entry): Prepend heading to
template if the template does not yet start with a heading.
* testing/lisp/test-org-capture.el (test-org-capture/entry): Add two
tests: no error is raised when org-capture is called with a template
that does not start with a
* lisp/org-capture.el (org-capture-place-table-line): Prepend
table-line begin ('|') if the template does not start with it.
* testing/lisp/test-org-capture.el (test-org-capture/table-line):
Verify that a template gets prepended with a '|' if it does not start
with it.
---
lisp/org-capture.el
Greg Minshall writes:
>> #+begin_src bash :results output :exports code :eval never-export
>> echo 'lf "\n"'
>> #+end_src
>
> it seems that `.man` files are in troff(1) format, which uses backslash
> escapes up the wazoo (however that is spelled). it seems that (one way)
> to getting a
Ihor Radchenko writes:
>> div's for toc (with role="org-toc") in subheadings par 1 and par 2 get the
>> same id : text-table-of-contents :
>
> Confirmed.
> Timothy, could you take a look?
> We could probably modify the id in `org-html-toc' when SCOPE is non-nil.
Fixed, on main.
On Thursday, April 11, 2024, Ihor Radchenko wrote:
> Christian Barthel writes:
>
>> I'd like to suggest adding a new prefix arg i.e.
>> `C-u C-u org-clone-subtree-with-item-shift' to reverse
>> the order of newly created / cloned siblings. Would
>> that be of interest for other orgmode users?
>
Hi, some time ago, I showed a screenshot how I am using
Org-Mode to manage my mastodon status updates
(posts/toos) [1] and I got some direct messages about
sharing my elisp functions and I publicly [2] stated
that the code is not production ready, but I will
rework this.
Sorry - it took a bit too
HI, full answer...
In the original code, that section prepends "style=" in some cases. I have
stumbled across
instances where the options started with style= because they were taken
directly from LaTeX
and the generated code ended by like:
\usepackage[style=style=numeric,backend=biber]{biblatex}
15 matches
Mail list logo
