Hi
In auctex+reftex it is possible that when I insert a new section header
a reference label is inserted automatically:
1. Example
\subsection{Inverse problem}
\label{sec:one}
2. And then using reftex-reference
I can insert \ref{sec:one}
So the equivalent of 1. in org mode
On Sun, Nov 14, 2021 at 3:10 PM Aaron Jensen wrote:
>
> On Sun, Nov 14, 2021 at 3:00 AM Ihor Radchenko wrote:
> >
> > Aaron Jensen writes:
> >
> > > Another one:
> > > https://gist.github.com/aaronjensen/5114997373008e18a6473f513f5d5da8
> > >
> > > I don't have the details of what I was doing
Hi all,
when I press [ or ] to add additional words to the agenda query but then
immediately abort the prompt with C-g without actually adding any new
word, a trailing extra space is added to the query. After doing the same
n times, the query includes n trailing spaces.
Best regards,
Carlos
> I don't see this in my agenda view. Image attached.
This is because there is a span in your case (Day). The space is still
there but it's not an extra one.
The space in:
" " ;; <- this is the extra space
'(:eval (org-agenda-span-name org-agenda-current-span))
Hi all,
with this content:
* a
** b1
c1
** b2
c2
** b3
c3
** b4
c4
** b5
c5
I create a sparse tree for c3: C-/ / c3
I get this:
* a...
** b3
c3
...
Expanding the three dots at the bottom:
* a...
** b3
c3
i should point out that my changes are old and i don't know if they
have already been done
On 11/16/21, Samuel Wales wrote:
> hmm i will have to try not setting o-e-r-c [ordinary user]. probably
> a lot of users do.
>
> might be useful to know whether a default regexp change could satisfy
>
hmm i will have to try not setting o-e-r-c [ordinary user]. probably
a lot of users do.
might be useful to know whether a default regexp change could satisfy
everybody? in my case i remove " and , from third re. i also have a
note "org-set-emph-re is what you are supposed to use, but it is
Hi all,
I don't see any clear reason why org-occur should hide unmatching
entries except at the top level, where it merely folds them. For files
containing lots of top-level entries this requires tree demoting in
order to hide irrelevant information, but this imposes constraints on
the tree
