From mboxrd@z Thu Jan 1 00:00:00 1970 From: Allen Li Subject: Re: New feature? Remove duplicate subheadings, preserving order Date: Tue, 2 Jan 2018 13:34:06 -0800 Message-ID: References: <87a7xxx5c5.fsf@nicolasgoaziou.fr> <87tvw5cu5t.fsf@nicolasgoaziou.fr> <87mv1wvr70.fsf@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43793) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWUCH-0005S2-2N for emacs-orgmode@gnu.org; Tue, 02 Jan 2018 16:34:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWUCG-00075X-6U for emacs-orgmode@gnu.org; Tue, 02 Jan 2018 16:34:09 -0500 Received: from mail-qt0-x22f.google.com ([2607:f8b0:400d:c0d::22f]:43088) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eWUCG-00075N-10 for emacs-orgmode@gnu.org; Tue, 02 Jan 2018 16:34:08 -0500 Received: by mail-qt0-x22f.google.com with SMTP id w10so64666867qtb.10 for ; Tue, 02 Jan 2018 13:34:07 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Robert Horn Cc: Adam Porter , emacs-orgmode@gnu.org On Tue, Jan 2, 2018 at 6:36 AM, Robert Horn wrote: > > Allen Li writes: > >> On Mon, Jan 1, 2018 at 8:07 PM, Adam Porter wrote: >> >> I don=E2=80=99t see a use case for checking all heading data. >> > > I can see such cases arising from templates and time tracking. I can > have a template that captures telephone calls. The call comes in and I > start the template. At this point the heading is just "Received Phone > Call" and a time tracking start. Time tracking is eventually kept in a > drawer, not in the headline. > > I might eventually go back an revise the headline based on notes from > the call, but that will not happen during the call. It's quite likely > that sorting out the calls will happen at the end of the day or the next > day. > > Similarly, I receive lab results. These will initially be a headline > with just "Lab Result", a time tag like CLOCK, and a tag to indicate > that it is a lab result. Some time later I might move them around to > attach them to a patient or project, but often by just moving them as > element into the right section for that patient or project. So these > also have the same headline contents and different headline data. It doesn=E2=80=99t sound like you end up with duplicates though? How do yo= u envision using duplicate removal for your workflows? In any case, it sounds like you want to assign unique IDs to each entry as suggested by Florian and remove duplicates using IDs instead of matching against heading data, which could collide through sheer luck.