From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: org-id fixups and minor changes Date: Sun, 01 Sep 2019 00:35:53 -0500 Message-ID: <877e6slgsm.fsf@alphapapa.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:37222) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i4IX0-0002Bx-UZ for emacs-orgmode@gnu.org; Sun, 01 Sep 2019 01:36:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i4IWz-0006WZ-SG for emacs-orgmode@gnu.org; Sun, 01 Sep 2019 01:36:06 -0400 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:58626 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i4IWz-0006VH-M4 for emacs-orgmode@gnu.org; Sun, 01 Sep 2019 01:36:05 -0400 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1i4IWw-000DRM-1K for emacs-orgmode@gnu.org; Sun, 01 Sep 2019 07:36:02 +0200 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: emacs-orgmode@gnu.org Gustav Wikström writes: > Yeah – you’re right, I didn’t think that much about automated ID > creation so I stopped at seconds. I agree that it would be more > general with more precision but that will also add some more noise > into each ID. Maybe that’s not significant. But I also wonder how > common it will be to try to batch-add ID’s…? I have nothing against > adding more precision though, if that’s requested. What do you think? For any one user, it probably won't cause a problem. But remember that Org is used by many people. If you add a method that can cause ID conflicts, it's inevitable that it will happen to someone eventually. It would be best to avoid conflicts in the first place. > I wouldn’t mind changing the default from random to timestamp. But I’m > not so sure about all the others? Please don't change the default, because the default works, and has for years. > One thing that complicates things is the way attachment functionality > parse the ID. If we use timestamps as the default ID it makes sense to > change the default way org-attach parses the ID into folders as > well. Something like “YYYY/MM/DD_and_the_rest”. But that will be a > breaking changing. The existing folder-structure for attachments > wouldn’t match the new any longer. Cleverness in code might solve the > breakage though… If there is interest in changing the default I can > try to solve the issue with the breaking change as well. Especially, please do not make a change like this. Attempted cleverness such as that should be avoided, because, considering how many users use Org, each with their own customizations and unique workflows, it's inevitable that such a change will lead to lost (or misplaced) data for some users. As a completely optional feature, it could be useful, however it would need to cope with both storage formats, because existing users would likely have data stored in the old locations when they enable the feature. Consider as well that more third-party software which uses Org formats is becoming popular, including non-Emacs software. Changes like these are much more likely to cause breakage and incompatibilities. For example, software like Orgzly and org-web are not yet even fully compatible with all of Org, but they make Org formats useful on platforms which are hard to use Emacs on. I think we should try not to make the work of those authors more difficult by making Org hard to keep up with. :)