emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clock connection between the files
Date: Sun, 24 May 2020 13:54:37 +0200	[thread overview]
Message-ID: <87lflhsg3m.fsf@gnu.org> (raw)
In-Reply-To: <CA+A2iZbGrVrfFgyKVubQAgyv0ib9Rq6rth4X_kn6t_UqU7UO9g@mail.gmail.com> (Vladimir Nikishkin's message of "Wed, 11 Mar 2020 10:15:11 +0800")

Hi Vladimir,

Vladimir Nikishkin <lockywolf@gmail.com> writes:

> How come org knows the connection between the first and the second
> file? There are not any references to the second file in the first one
> whatsoever.

I cannot reproduce the problem.  Can you reproduce it (without adding
that much contents to the second file)?  Otherwise I don't see where
the error can come from.



  reply	other threads:[~2020-05-24 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11  2:15 Vladimir Nikishkin
2020-05-24 11:54 ` Bastien [this message]
2020-05-24 13:37   ` Vladimir Nikishkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lflhsg3m.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=lockywolf@gmail.com \
    --subject='Re: Clock connection between the files' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).