From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Everaert Subject: Re: [Idea] Org Collections Date: Mon, 23 Dec 2019 14:31:55 +0100 Message-ID: <87imm7jhh8.fsf@gmail.com> References: <87tv60ldf2.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:49841) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ijNoe-0008Kc-2r for emacs-orgmode@gnu.org; Mon, 23 Dec 2019 08:32:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ijNoc-0005Rz-Qt for emacs-orgmode@gnu.org; Mon, 23 Dec 2019 08:32:07 -0500 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]:33134) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ijNoc-0005QO-If for emacs-orgmode@gnu.org; Mon, 23 Dec 2019 08:32:06 -0500 Received: by mail-wm1-x32d.google.com with SMTP id d139so14843803wmd.0 for ; Mon, 23 Dec 2019 05:32:04 -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: Gustav =?utf-8?Q?Wikstr=C3=B6m?= Cc: "emacs-orgmode@gnu.org" Gustav Wikstr=C3=B6m writes: > Hi! > >> -----Original Message----- >> From: Emacs-orgmode On = Behalf >> Of Roland Everaert >> Sent: den 16 december 2019 12:26 >> To: emacs-orgmode@gnu.org >> Subject: Re: [Idea] Org Collections >>=20 >> +1 for this idea. >>=20 >> You speak about one document used by multiple collections, how do you >> plan to manage that from a file system point of view? > > The idea was to let the user define the scope of each collection herself.= Similar to how an agenda is defined today (Maybe in the same way even?). M= ost simple configuration would be to let a collection be one folder. But in= the end it would be up to the imagination of and usefulness for the user. = Having one document in multiple collections wouldn't be any issue because t= he collections are only pointing to locations of files in the filesystem. A= nd if creating overlap between collections sounds dumb then it's a simple c= hoice by the user to not do it! Have you had a look at org-brain. I don't use is much, but there are some overlapping functionnality to merge, maybe. > >> How will be organized a collection, still from the FS point of view? > > Maybe the comments above answer that as well? > >> As some are delving into the abyss of sementic, I propose aspects >> instead of collections or contexts. Ultimately we are trying to manage >> various aspects of our life, by splitting those aspects into files or >> diretories and what not. So, if it is the intent of your idea, the term >> aspect seems more appropriate than collection or context IMHO. > > Many words could work. Context, Project, Group, Aspect, Areas, etc. I fir= st thought of the name "project" to match the Projectile package. But I thi= nk collection is a better concept here. It lets the user think not of how i= t should be used but rather of what it consists. Which is a collection of f= iles (and settings). That collection can ofc. be used for project, as aspec= ts, or be seen as contexts or areas. So in my mind collection is the broade= r, more applicable term. It has less subjective meaning attached to how thi= s functionality could be used. It IS a collection but can be USED as aspect= s, for projects, etc. What do you say? =F0=9F=98=8A I think I can live with it ;) > >>=20 >> Did you think about the specific UI of aspects management? >> Proposal of UI I particularly like: >> - Mu4E >> - forge/magit > > Not really.. Except I agree with you on magit. The other I haven't used. Mu4E is a major mode for managing e-mails using the mu index. it provides a main view with bookmarks and entries to perform searches and composing message, among othe thing, but what I find more useful are the header view, which displays a multi-columns list of e-mails with associated meta-data and a message view allowing to view the content of an e-mail. The header view allows for bulk actions while the message view act, obiously, on the current message and permit replying and transfering the current e-mail. > >>=20 >> How to keep track of all those aspects? > > My first thought was to define them in a simple list. > >>=20 >> I will surely have more to say, but, as of know I am at work. >>=20 >> Regards, >>=20 >> Roland. > > Thanks for your comments! > > Regards > Gustav --=20 Luke, use the FOSS Sent from Emacs