emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [PATCH] Add info when reference to remote table is not in the file
Date: Fri, 06 Apr 2012 10:36:35 +0200	[thread overview]
Message-ID: <80398h8df0.fsf@somewhere.org> (raw)
In-Reply-To: 87sjghjof3.fsf@gnu.org

Hi Bastien,

Bastien wrote:
> thanks for the patch.
> I wonder if we should trigger an error instead -- why a message?

Because it's not an error... When a reference (I guess it always must be an
ID, then) is not found locally, Org will search for it in external known

The problem is you see hundreds of messages "Finding ID location...", and you
don't know which reference Org is trying to find...

When you have multiple tables, with multiple references, this is a nightmare
to find which was is wrong.

Just use `TBLNAME' instead of `tblname' for the referenced table (or the
inverse, if you apply the patch you sent me a couple of days ago), and you'll
understand that it's good to know what Org is searching for.

> (I don't like using sit-for, it's often worse than getting an error...)

I don't like it that much either, but, here, it's the only way to see the
message before being flooded by the "Finding ID location..." messages.

Best regards,

Sebastien Vauban

  reply	other threads:[~2012-04-06  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 14:07 [PATCH] Add info when reference to remote table is not in the file Sebastien Vauban
2012-04-06  7:43 ` Bastien
2012-04-06  8:36   ` Sebastien Vauban [this message]
2012-04-09 16:01     ` Bastien
2012-04-19 14:10       ` Sebastien Vauban
2012-04-19 14:27         ` Sebastien Vauban
2012-04-19 14:29           ` Nicolas Goaziou
2012-04-21 13:43           ` Bastien
2012-04-23 13:07           ` Bastien

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=80398h8df0.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).