Hello,
> There are still known problems though. The patch currently breaks many
> org-mode tests when running =make test=. It is partially because some
> tests assume overlays to be used for folding and partially because the
> patch appears to break certain folding conventions. I am still
>
third question:
if you capture a completely blank capture buffer, is it supposed to
insert a blank line right after the target headline, or is it supposed
to be a no-op? [i prefer no-op.]
fourth question:
if you capture a capture buffer with a newline, [same options]. [i
prefer no-op.]
this
i want to check on what is /supposed/ to occur in 9.4 maint.
if i capture an entry that has a newline at the end of the last line
in the entry, is it supposed to end the entry with a blank line? or
is it supposed to end the entry with the last line? [i want last
line.]
if i capture an entry
Kyle Meyer writes:
> The following patch should restore the previous behavior. I'll apply it
> in a couple of days if no objections come in.
>
> -- >8 --
> Subject: [PATCH] org.el: Fix regression in handling of empty #+TAGS
Pushed (3eccc537c).
James N. V. Cash writes:
> Kyle Meyer writes:
>> Okay, so when eldoc-documentation-functions is defined (Emacs >=28), we
>> take the first function and go with it. That might not be exactly what
>> you'd see in the native buffer, depending on whether there are other
>> members of
After letting it sit, I'm not sure that my patch above is a good idea
anymore. While it would be useful, it also adds substantial complexity
to ob-python.
For now, I think I prefer to keep ob-python leaner, so am going to hold
off on this.
An alternative approach is to have the user handle
Dear Compeers,
I am writing a document in texinfo, but I also have some commands in
Org-Mode so that if I change my Emacs Major Mode to Org-Mode
I get an easy way to traverse my texinfo code. However I would like
to keep the syntax highlighting as the use set for texinfo, rather than
that of
Thanks for the patch!
I noticed the patch also works for org-link, which had been a headache for me.
On Fri, Sep 18, 2020, at 04:52, Protesilaos Stavrou wrote:
> Ihor Radchenko [2020-09-17, 16:25 +0800]:
>
> > The attached patch seems to fix the issue.
> > Can anyone test?
I also tested, with
Abstract
This is a fix for a problem regarding the org-preview-latex-fragment
function and its associated org-preview-latex-process-alist item
'dvipng,' which is broken by imported packages from
org-latex-packages-alist which are incompatible with the 'latex'
command
Context
Relevant
I can reproduce this. I'm on the most recent master with Emacs 28.0.50. Once
the last line is deleted, org-cycle won't show the "**" line and the minibuffer
continues to say "FOLDING" instead of cycling through the various states.
On Sat, Sep 19, 2020, at 12:10, B Goodr wrote:
> Hi,
>
> Still
Hi,
Still loving Org mode!! Keep up the good work.
Here is a bug, though:
Steps to reproduce:
Store the following into some .org file (in between the "cut-here" lines):
---cut-here---cut-here---cut-here---cut-here---cut-here---cut-here---
* TODO aaa bbb ccc
** TODO aaa bbb ccc
On 9/19/2020 9:50 AM, Leon Weber wrote:
> Hi together, I recently updated from org-mode version 9.1.8 to 9.3. I
> noticed a problem with group tags / tag hierarchy in the agenda-view
> (Agenda for current week or day).
>
> Example File:
> --
> #+TAGS: [ PARENT : CHILD1 CHILD2 ]
> *
Hi together, I recently updated from org-mode version 9.1.8 to 9.3. I
noticed a problem with group tags / tag hierarchy in the agenda-view
(Agenda for current week or day).
Example File:
--
#+TAGS: [ PARENT : CHILD1 CHILD2 ]
* test1 :CHILD1:
SCHEDULED: <2020-09-14 Mon>
* test2
13 matches
Mail list logo
