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.
-
Hi Branden,
On Sat Jan 4, 2025 at 7:37 AM CET, G. Branden Robinson wrote:
> At 2025-01-04T01:23:02+0100, onf wrote:
> [...]
> > Speaking of the left italic correction (\,), could you please give me
> > some example(s) where it's actually useful? I have yet to see a single
> > instance where it cha
Ihor Radchenko writes:
> "Dr. Arne Babenhauserheide" writes:
>
>>> Why? What's wrong with `org-element-begin' and `org-element-end'?
>>
>> I didn’t know that I could also use these ☺
>>
>> What’s wrong is only that I had to fix showing the first paragraph of
>> articles on my website with this c
"Loris Bennett" writes:
> I have been using Orgmode for several years to record my working hours
> and calculate how much overtime I have accrued. The mechanism is rather
> rudimentary, in that I clock in and out of 'work' to record start and
> end times each day and then copy these times into a
Michael Maurer writes:
> Is there no way to specify when scheduled habits show up in my agenda?
Nothing specific to habits, AFAIK.
> org-habit-preceding-days is just for the visual property of the graph?
Yup.
You may consider custom `org-agenda-skip-function'.
--
Ihor Radchenko // yantar92,
Dave Kemper writes:
> On Sat, Jan 4, 2025 at 7:24 AM Ihor Radchenko wrote:
>> "G. Branden Robinson" writes:
>> > So another thing to know here is that these italic correction escape
>> > sequences are, yet again, GNU troff extensions. A legacy formatter is
>> > likely to render them as if the
On Sat, Jan 4, 2025 at 10:39 AM Max Nikulin wrote:
>
> On 29/12/2024 11:26, Nikolaos Chatzikonstantinou wrote:
> > I should probably try to do this, but I got inspired by Worg's website
> > which does not do any backend hacking as far as I can tell, but
> > instead puts some javascript to collapse
On Sat, Jan 4, 2025 at 7:24 AM Ihor Radchenko wrote:
> "G. Branden Robinson" writes:
> > So another thing to know here is that these italic correction escape
> > sequences are, yet again, GNU troff extensions. A legacy formatter is
> > likely to render them as if the backslash were absent, which
On 29/12/2024 11:26, Nikolaos Chatzikonstantinou wrote:
I should probably try to do this, but I got inspired by Worg's website
which does not do any backend hacking as far as I can tell, but
instead puts some javascript to collapse the table of contents.
Not all users are happy with current CSS
Björn Bidar writes:
>> Both alignment and width are derived from LINK AST node.
>> I am not sure what is the problem.
>> AFAIU, Karthik is simply asking why you decided to calculate alignment
>> from LINK, but not width.
>
> My question was because the width is set through the width of the inline
"Suhail Singh" writes:
> * lisp/org-lint.el (org-lint-invalid-macro-argument-and-template):
> Ensure templates defined in org-export-global-macros are included
> during macro initialization.
Applied, onto main.
Thanks!
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=358eeb7ce8
-
writes:
the_wurfkreuz via "General discussions about Org-mode."
> 1. oariseatnoarise ntoaris en
> 2. aoirsetnaorisetnoarisetn
> Then from the end of the second item use org-return, the pointer position is
> going to be indented like this:
>
> 1. oariseatnoarise ntoaris en
> 2. aoirsetnaorisetnoa
"G. Branden Robinson" writes:
>> Also note that if a change involving italic happens between two
>> non-whitespace characters, like so:
>> groff(/7/)
>>
>> ...an italic correction should be emitted to prevent the two glyphs
>> colliding into each other:
>> groff(\,\fI7\fR\/)
>> where:
>> \
Pedro Andres Aranda Gutierrez writes:
> yes, the patch is just a step towards consistency, but I think is is an
> important one, because it
> makes org-mode not generate illegal/faulty LaTeX code.
Right, but it is also kind of half-way between "Org export default" and
"LaTeX" behaviors. If it is
John C writes:
> Thanks for the feedback. See updated org-matlab.patch. Note code evaluation
> will now error out when using an out-of-date matlab-mode (rather than
> generating a warning) because when using an older matlab-mode, code block
> evaluation doesn't work. We need to wait for the matla
"G. Branden Robinson" writes:
>> ...
>> (4) will produce a man file named after the .org file, in the same
>> directory.
>
> Thank you very much. I'll test out my proposed changes locally.
Note that the official Org mode repository is on savannah.
See https://orgmode.org/worg/org-contribute.ht
"G. Branden Robinson" writes:
>> Then maybe we can put .sp explicitly instead of a blank line.
>
> I advise against it. If what follows is a paragraph or a (sub)section
> heading, then by calling the applicable macro, you will get any
> necessary vertical space automatically.
>
> Also, on typese
There is another problem though. Consider: 1. M-x org-lint
2. Switch back to the original .org buffer 3. M-g M-n 4. Observe
link report and .org window swapped and point moving back
to the lint report. It is not what usually happens with error
navigation (e.g. during compile or grep na
18 matches
Mail list logo
