On Fri, Oct 9, 2020 at 6:40 PM Samuel Loury wrote:
> > I almost always choose 'k' (keep) and it is often not responding after
> the
> > first or several presses. But as Samuel Loury pointed out, I'll try
> > pressing ten times at least, the next time it happens.
>
> IIRC, pressing 'k', even a lot
On Fri, Oct 9, 2020 at 9:35 AM Ihor Radchenko wrote:
> > Thanks for the tip, I'll try pressing 10 times the next time it happens
> > (which is probably today).
>
> That sounds really odd. Could it be that there are multiple open
> (without ending time) clocks existing in your org files?
>
>
I nev
On Fri, Sep 4, 2020 at 9:47 PM Bastien wrote:
> Hi Budiman,
>
> Budiman Snowman writes:
>
> > One way I know is using a unique dedicated target, e.g.:
> >
> > * topic1
> > See topic [[topic2]].
> > See glossary [[glossary topic2][topic2]].
> &
On Thu, Oct 8, 2020 at 10:30 PM Eric S Fraga wrote:
> On Thursday, 8 Oct 2020 at 16:54, Samuel Loury wrote:
> > Also, another boring behavior of org-resolve-clocks is that I generally
> > have to press several times (about ten times) on the "i" key to ignore
> > the message.
>
> Similar with the
On Thu, Oct 8, 2020 at 9:54 PM Samuel Loury wrote:
> Hi,
>
> Actually, I realized though that even though the client was appearing
> frozen, by pressing several times on "i" (ten times also), it eventually
> closes the resolve clock stuff and let me play with emacs like nothing
> happened. Then,
I use emacsclient (with Konsole tabs, if that matters). I usually have
several emacsclient instances open in different tabs. When I start a clock
and then get away long enough, Emacs will prompt me to resolve the idle
time in different buffer that has the clock, usually in the first buffer
that I
On Wed, Jun 3, 2020 at 9:21 PM Diego Zamboni wrote:
> I almost always use a CUSTOM_ID property for this, e.g.
>
> * topic1
> See topic [[#topic2][topic2]].
> See glossary [[#glossary_topic2][topic2]].
>
> * topic2
> :PROPERTIES:
> :CUSTOM_ID: topic2
> :END:
>
> * glossary
> ** topic1
> :PROPERTIE
On Thu, Jun 4, 2020 at 11:31 AM Kyle Meyer wrote:
> Budiman Snowman writes:
>
> > Suppose I have this document:
> >
> > * topic1 :tag1:tag2:tag3:
> > * topic2
I have this document:
* topic1
See topic [[topic2]].
See glossary [[topic2]].
* topic2
* glossary
** topic1
** topic2
What are ways to disambiguate the internal links? The first link should
link to the topic2 first-level entry, while the second link should go to
the topic2 entry under glossary.
Suppose I have this document:
* topic1 :tag1:tag2:tag3:
* topic2 :tag1:tag2:tag4:
* topic3 :tag1:tag3:tag4:
* topic4
10 matches
Mail list logo
