Hi,
> -Original Message-
> From: Roland Everaert
> Sent: den 23 december 2019 14:32
> To: Gustav Wikström
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [Idea] Org Collections
> Have you had a look at org-brain. I don't use is much, but there are some
> overla
Gustav Wikström 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
>>
>> +1 for
On 14 December 2019, Gustav Wikström wrote:
2 Idea
==
I propose to introduce `Collection' as a concept in the realm of Org
mode. [1]
This is very interesting, and I think I have some cases where I could use this.
When there's something to test, I'll certainly try it. It's a good idea,
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
>
> +1 for this idea.
>
> You speak about one document used by multiple col
I do agree that "aspect" is a very abstract term and all depends on the
scope of this proposal, I suppose.
Reading the proposal again, it seems that my proposal could apply, as
the intent seems to define a per "aspect" configuration. On the other
end as aspects are quite abstract, an aspect can be
I would have to say the hardest thing I ever have to do as a developer
is naming things. It is hard enough to do within a context of a single
group, even harder when speaking about something with a global user base
(language, social/cultural differences etc). Despite this, it is so very
important
+1 for this idea.
You speak about one document used by multiple collections, how do you
plan to manage that from a file system point of view?
How will be organized a collection, still from the FS point of view?
As some are delving into the abyss of sementic, I propose aspects
instead of collecti
+1, that is: This is an interesting idea, there have been times when I
might have found something like this handy, and I might well use if it's
developed, though I'm not sure if it will ease my cognitive load or add
to it. :-)
Yours,
Christian Moe
Gustav Wikström writes:
[...]
__
haven’t thought that there
should be a syntax for that either.
But please explain more on what you think, if I misunderstood you!
/Gustav
From: John Sturdy
Sent: den 15 december 2019 13:14
To: Gustav Wikström
Cc: emacs-orgmode@gnu.org
Subject: Re: [Idea] Org Collections
That seems
Hi Adam,
> -Original Message-
> From: Emacs-orgmode On
> Behalf Of Adam Porter
> Sent: den 15 december 2019 12:01
> To: emacs-orgmode@gnu.org
> Subject: Re: [Idea] Org Collections
>
> How does this idea compare with Akira Komamura's org-starter package?
&
better. But
not sure yet how to realize it. Thinking in progress.
Thanks
Gustav
From: Emacs-orgmode On Behalf Of
tbanelwebmin
Sent: den 15 december 2019 10:08
To: emacs-orgmode@gnu.org
Subject: Re: [Idea] Org Collections
Interesting idea!
Is everyone aware of Emacs Projectile?
https
That seems hierarchical, which is ok (as in org-mode itself) but how about
implementing a more general graph mechanism, which could be used to do this
but more flexibly?
On Sat, 14 Dec 2019, 21:04 Gustav Wikström, wrote:
> Hi list and all honored readers!
>
> I have an idea. One that I've mentio
How does this idea compare with Akira Komamura's org-starter package?
https://github.com/akirak/org-starter
Its readme begins:
> Org-starter is a framework for basic configuration of Emacs Org
> Mode. It allows you to configure Org Mode easily even with many files
> and directories.
> The stand
Interesting idea!
Is everyone aware of Emacs Projectile?
https://github.com/bbatsov/projectile
Not exactly the Org Collections you talks about, Gustav,
but somehow related.
Projectile manages collections of files that belong
togeth
Tim Cross writes:
[...]
> Its a +1 from me.
And me -- I use Org across so many different contexts (in fact, I'd
propose the name org-contexts over org-collections \end{bikeshed}),
sometimes using the /same data in different contexts/, and while Org has
good tools for localizing config options
In general, I like the idea. While you are correct that most of what you
refer to can be achieved using existing org functionality, I like the
clear separation 'collections' would offer - it is like a namespace for
a collection of org documents. I like the idea of being able to isolate
customizat
16 matches
Mail list logo
