all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xebar Saram <zeltakc@gmail.com>
To: Philip Hudson <phil.hudson@iname.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: issues with duplicate ID's
Date: Fri, 22 Jul 2016 20:46:29 +0300	[thread overview]
Message-ID: <CAOQHXPrLQzjRMfewi8tj+pH5xiogA=CLfcReOxQG7-CkhM_D+g@mail.gmail.com> (raw)
In-Reply-To: <CAJ1MqVG5ryr6xucXCOCdO1R2LLg+aZO8EshzRF5y2FVOXjz_9Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

thx
it seems many of them are in the corresponding archive files. isnt that
normal when you archive?

best

Z

On Fri, Jul 22, 2016 at 6:20 PM, Philip Hudson <phil.hudson@iname.com>
wrote:

> On 22 July 2016 at 12:58, Xebar Saram <zeltakc@gmail.com> wrote:
> > Hi all
> >
> > i have been having many warnings on Duplicate ID's past month and finally
> > have time/energy to ask about this ;-)
> >
> > so each time i start emacs or switch org buffers i get a ton of warnings
> on
> > Duplicate ID's:
> >
> ...
> >
> > 2 questions
> >
> > a) does this have any affect on orgmode performance or other effects i
> cant
> > think of?
>
> Breaks MobileOrg, for one.
>
> > b) any intelligent way of resolving this?
>
> Assuming they are all programmatically assigned and not explicitly
> referenced by you anywhere: delete all the IDs. New ones will be
> assigned.
>
>
> --
> Phil Hudson                   http://hudson-it.ddns.net
> @UWascalWabbit                 PGP/GnuPG ID: 0x887DCA63
>

[-- Attachment #2: Type: text/html, Size: 1732 bytes --]

  reply	other threads:[~2016-07-22 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 11:58 issues with duplicate ID's Xebar Saram
2016-07-22 15:20 ` Philip Hudson
2016-07-22 17:46   ` Xebar Saram [this message]
2016-07-23  7:02     ` Xebar Saram
2016-07-23 13:04       ` Philip Hudson

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to='CAOQHXPrLQzjRMfewi8tj+pH5xiogA=CLfcReOxQG7-CkhM_D+g@mail.gmail.com' \
    --to=zeltakc@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=phil.hudson@iname.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.