Hello,
Yes, that clarifies things quite a bit. I thought that the contents of the list
item only included that specific item, when in reality it includes the item and
all sub-lists.
Thanks,
Rohit
th spaces,
it repeats the list marker (** for a second level nested list, *** for 3 levels
of nesting, etc).
Thanks,
Rohit Patnaik
n't realize that `make update`
was an option.
-- Rohit Patnaik
Confirmed fixed.
Thanks for the quick turnaround!
Rohit
, the
fontification behaving as it should.
Thanks,
Rohit Patnaik
> This is because ox-md adds a blank line between almost every element,
> including table-rows (which ox-md does not care about).
> Fixed, on bugfix.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=85aafac41
Thanks for fixing this. I completely forgot that my export code is a
generated by the code is:
#+begin_example
||Col 1 || Col 2 || Col 3||
||left aligned cell || centered cell || right aligned cell||
#+end_example
The contents of each cell are formatted correctly, but there's an additional
newline between the two rows. How do I prevent this newline from being added?
Thanks,
Rohit Patnaik
> Fixed, on main; for Emacs >=29. Will not be fixed for earlier Emacs versions.
I've confirmed that it's fixed. Thanks so much for the fast turnaround!
Rohit Patnaik
-pc-linux-gnu, X toolkit, cairo version 1.17.8,
Xaw3d scroll bars) of 2023-08-02
My operating system is Fedora Linux 39, running Gnome 45.3 on Wayland.
Thanks,
Rohit Patnaik
I also want to chip in with a thank-you for the org syntax specification page.
As someone who's working on a custom org exporter, this is a very useful
resource for finding out how elements are structured within org-mode.
Thanks,
Rohit
> (not a scheduled one, since I don't need to do it on a particular date)
The `SCHEDULED' property is in fact the correct way to indicate that you wish to
hide the task from the global to-do list until a particular date. `SCHEDULED'
indicates the day upon which you wish to start working on the
> org-agenda-switch-to jumps to the actual agenda match (usually a timestamp).
> It may or may not be close to the headline (think of active timestamp inside
> notes). Such behaviour, albeit undocumented, may be useful for some users. I'd
> rather not change it.
Okay, that makes sense.
>
I've gotten back into using org-agenda to manage my todos, and I noticed an odd
discrepancy in behavior. When I hit RET in the agenda buffer to go to the TODO
entry in the original org file, I see that the point is on the DEADLINE line.
However, when I hit TAB, I find that the point is placed
As I understand it, the bug is in `org-md-item'. It formats the tag portion of
the
description with **%s**, and then simply concatenates the content. This is fine
when the content is a simple string, but when the content includes line breaks
(i.e. when content is itself a list), it doesn't
I'm looking at function that handles transcoding inline code and verbatim text
in ox-md:
(defun org-md-verbatim (verbatim _contents _info)
"Transcode VERBATIM object into Markdown format.
CONTENTS is nil. INFO is a plist used as a communication
channel."
(let ((value (org-element-property
Could you do this with a mode-hook? Something like:
(add-hook 'org-mode-hook
(lambda ()
(when (memq (buffer-file-name) 'list-of-files-to-not-highlight)
(font-lock-mode -1
-- Rohit
Thanks so much for making those changes and getting it merged.
-- Rohit
> Since md backend is derived from html, is it necessary to define an
> option specific to markdown or the value defined for HTML may be reused?
> I am unsure which variant will be more convenient, so it is not more
> than an idea that may be easily discarded.
I considered reusing the value
> This contribution will be welcome.
I've attached a patch which implements the change. I followed the pattern that
ox-html uses to the greatest extent possible. I tested it by exporting org-mode
files to markdown with the table of contents both enabled and disabled. I
didn't see any errors, and
from making this change.
Thanks,
Rohit Patnaik
f_002dday-specifications.html#Time_002dof_002dday-specifications>
> On Apr 24, 2018, at 2:11 PM, Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Rohit Patnaik <quanti...@quanticle.net> writes:
>
>> Hello,
>>
>> According to the
time prefix, which results in the text appearing garbled.
Thanks,
Rohit Patnaik
22 matches
Mail list logo
