e prefix, which results in the text appearing garbled.
Thanks,
Rohit Patnaik
f_002dday-specifications.html#Time_002dof_002dday-specifications>
> On Apr 24, 2018, at 2:11 PM, Nicolas Goaziou wrote:
>
> Hello,
>
> Rohit Patnaik writes:
>
>> Hello,
>>
>> According to the org-mode manual:
>>
>>> In the headline of the
major
issues that might arise from making this change.
Thanks,
Rohit Patnaik
> 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 I
> 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 fro
Thanks so much for making those changes and getting it merged.
-- Rohit
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
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 :v
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 realize
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 at
> 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.
> Recenter
> (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 tas
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
86_64-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
> 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
e
However, the actual output 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
> 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
, the
fontification behaving as it should.
Thanks,
Rohit Patnaik
Confirmed fixed.
Thanks for the quick turnaround!
Rohit
n't realize that `make update`
was an option.
-- Rohit Patnaik
o that instead of indenting with spaces,
it repeats the list marker (** for a second level nested list, *** for 3 levels
of nesting, etc).
Thanks,
Rohit Patnaik
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
delete Sub-item 3 and update the Item
1 checkbox all at once. Right now, I have to move the cursor back up to Item 1
and hit C-c C-c to force the checkbox to update.
Thanks,
Rohit Patnaik
n element, marker or buffer position, and sets a property there, creating
the property drawer if necessary.
Thanks,
Rohit Patnaik
Hello,
When I was looking at the diff for 8e141ec24e, I noticed that there was a second
typo on line 181 of =etc/ORG-NEWS=. This patch fixes it.
Thanks,
Rohit PatnaikFrom 9eee3b09681e1e1f61d58932878e0f2df01e5f0f Mon Sep 17 00:00:00 2001
From: Rohit Patnaik
Date: Sat, 28 Dec 2024 13:20:32 -0600
Relatedly, would the refactored fontification also handle nested bold and italic
text where the delimiters for those are adjacent to one another?
Right now, for example:
/this is italic *and some bold italic*/
is only fontified in Emacs as italic. The portion of the text that is meant to
be
Org-publish, by default, only processes org files. If you want to include CSS
files, images, and other non-org content, you need to process them as
attachments.
So, for example, this is what I have:
(setq org-publish-project-alist
'(("website-orgfiles"
:base-directory "$HOME/website_src/"
essary news and documentation updates.
Thanks,
Rohit PatnaikFrom f8c1f2919d8aa07e6f73ad5b097f8da2bb1ca3ee Mon Sep 17 00:00:00 2001
From: Rohit Patnaik
Date: Tue, 18 Mar 2025 04:45:06 -0500
Subject: [PATCH] org-clock: Make headline truncation behave better
* lisp/org-clock.el (org-clock-get-clock-st
Hello everyone,
I know that I can use the `:block' option to change the time span considered by
a clock table to specific days, or even a specific week, by specifying e.g.
`2007-W50'. However, I would like to create a clock table that spans a two week
period, e.g. from 2025-04-07 to 2025-04-21.
Ah, sorry for the noise, I figured out what my problem was. I'd tried
specifying :tstart and :tend, per the manual, but my initial attempt to do so
resulted in the following error:
org-clock-get-table-data: Wrong type argument: stringp, <2025-04-06
However, after rereading the manual more clo
I have updated the docstring for org-clock-get-clock-string, which I'd forgotten
to do in the previous version of the patch.
Thanks,
RohitFrom ba1662b116e8c0601c7f174d379005ac767f7f52 Mon Sep 17 00:00:00 2001
From: Rohit Patnaik
Date: Tue, 18 Mar 2025 04:45:06 -0500
Subject: [PATCH] org-
I tried opening the linked file with the latest org-mode from git, as of commit
53cd3f83c96728 and I was not able to reproduce the issue. I was able to open the
file, move around in it, make edits, etc. without any problems.
However, I am using Emacs 29.4, not 30.1. Could that have something to do
es surrounding the headline. I've
updated the code to use a variable (`spaces-and-parens-length') for that
instead.
I have also added a preliminary news entry and I've updated the commit message
to reflect the above changes.
Thanks,
RohitFrom 6be426ea88018e168a5ae7775f4bcc3756cde
I'm against moving to `luatex' as the default compiler. I'm decently familiar
with LaTeX, having used it to write papers and even my resume. I just tried
to compile a relatively simple LaTeX file using `luatex' on my Fedora Linux
machine with the `texlive-full' package installed. I got a bunch o
Oops, my mistake. I was actually calling `luatex' instead of `lualatex'. The
document compiles fine with `lualatex'. However, noted, it did take noticeably
longer.
Thanks,
Rohit
the code looks much better now.
RohitFrom 727ec7fb129e9c09617c204537eb1b2e5ed24ddb Mon Sep 17 00:00:00 2001
From: Rohit Patnaik
Date: Tue, 18 Mar 2025 04:45:06 -0500
Subject: [PATCH] org-clock: Make headline truncation behave better
* lisp/org-clock.el (org-clock-get-clock-string): Move the headline truncat
p anything in the merge process.
Thanks,
RohitFrom 17cd390ab54edc6713d09fff36ad0eddc9510b53 Mon Sep 17 00:00:00 2001
From: Rohit Patnaik
Date: Tue, 18 Mar 2025 04:45:06 -0500
Subject: [PATCH] org-clock: Make headline truncation behave better
* lisp/org-clock.el (org-clock-get-clock-string): Mov
> Applied, onto main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=7eafc194d
Thanks so much! This was a long-standing minor annoyance of mine, and it's great
to have the fix upstream.
Thanks,
Rohit
Hello,
I looked up Captain mode and it seems like the problem is that the default
sentence start function =(car (bound-of-thing-at-point 'sentence))= finds the
list marker as the start of the given sentence.
It is possible to override that behavior. The mode defines a variable,
=captain-sentence-
39 matches
Mail list logo
