Tim Cross writes:
>> I don't see how that would possible once it is integrated in GNU emacs
>> core, there will be no separate makefile or anything of that sort, but
>> maybe I am missing something.
>>
>
> There is going to have to be a way for people to maintain and build org
> independently. Wh
Tim Cross writes:
> Just to throw my 2 cents in.
>
> While I can understand the benefits of being able to easily install the
> latest org package via elpa, I think there are some significant benefits
> to org being a part of core Emacs.
>
> I currently find three issues with the current situation
Bastien Guerry writes:
> Hi Philip,
>
> phillip.l...@russet.org.uk (Phillip Lord) writes:
>
>> I presume you do see this as an advantage? The issue is, surely,
>> that it's too much of a PITA for the advantage that you gain?
>
> Well, it's not really about PITA-or-not-PITA, it's just that I want
Hi Robert,
first of all, my bad: what I should have said in all these discussion
is that any decision regarding moving Org to Emacs' core won't happen
any time soon (I'd say two or three years).
Keeping Emacs master branch in sync with Org maint branch is not a
problem anymore, so the decision of
Uwe Brauer writes:
"qTim" == qTim Cross writes:
>
>> Just to throw my 2 cents in.
>
>> 1. Problems with mixed versions. Currently, Emacs has org 8.x included
>> in the distribution. This is despite 9.x being out before the release of
>> 25.2. Something needs to be done to im
Indeed I admit that I might have exagerated when I called it
"average". Please excuse my wrong doing. :)
Adonay Felipe Nogueira writes:
> I have just thought of some more advantages and disadvantages too.
>
> * Strengths
>
> ** One less split in development effort
>
> This one explains itself. Also, for a related article against "forking",
> "bundling", and "reinventing the wheel" practices, see
> [
Also, all the issues related to updates and compatibility would be
solved if more poeple used GNU Guix package manager. This way, GNU Emacs
can integrate Org in its core, and use the "1 release per 9 months"
cycle, and also could have package recipes pointing to arbitrary commits
if there is a crit
Bastien Guerry writes:
> Hi Philip,
>
> phillip.l...@russet.org.uk (Phillip Lord) writes:
>
>> I presume you do see this as an advantage? The issue is, surely,
>> that it's too much of a PITA for the advantage that you gain?
>
> Well, it's not really about PITA-or-not-PITA, it's just that I want
>>> "qTim" == qTim Cross writes:
> Just to throw my 2 cents in.
> 1. Problems with mixed versions. Currently, Emacs has org 8.x included
> in the distribution. This is despite 9.x being out before the release of
> 25.2. Something needs to be done to improve coordination and perhaps i
I have just thought of some more advantages and disadvantages too.
* Strengths
** One less split in development effort
This one explains itself. Also, for a related article against "forking",
"bundling", and "reinventing the wheel" practices, see
[[https://wingolog.org/archives/2015/11/09/embrac
On Monday, 3 Jul 2017 at 12:40, Bastien Guerry wrote:
[...]
> Well, it's not really about PITA-or-not-PITA, it's just that I want
> org-mode to be the default mode for some files in Emacs, and having
> org-mode in Emacs' core is the most simple way to go for this.
This, I must admit, is quite a
Just to throw my 2 cents in.
While I can understand the benefits of being able to easily install the
latest org package via elpa, I think there are some significant benefits
to org being a part of core Emacs.
I currently find three issues with the current situation which may be
somewhat resolved
Hi Philip,
phillip.l...@russet.org.uk (Phillip Lord) writes:
> I presume you do see this as an advantage? The issue is, surely,
> that it's too much of a PITA for the advantage that you gain?
Well, it's not really about PITA-or-not-PITA, it's just that I want
org-mode to be the default mode for
Bastien writes:
> Hi Uwe,
>
> Uwe Brauer writes:
>
>> I am not sure whether I understand that discussion in emacs dev
>> correctly. Will orgmode be moved into the GNU emacs try as it was done
>> with gnus?
>
> for the record, I would be in favor of this. Why?
>
> - Less installation headaches
>
"ESF" == Eric S Fraga writes:
ESF> On Monday, 3 Jul 2017 at 08:33, Uwe Brauer wrote:
>> But the release cycles are very different, so in order to have always
>> the latest stable org package, I need to compile and install the whole
>> GNU emacs beast. I thought the whole idea of a package system
On Monday, 3 Jul 2017 at 08:33, Uwe Brauer wrote:
> But the release cycles are very different, so in order to have always
> the latest stable org package, I need to compile and install the whole
> GNU emacs beast. I thought the whole idea of a package system is to
> avoid this headache.
I agree.
>>> "Bastien" == Bastien writes:
> Hi Uwe,
> Uwe Brauer writes:
>> I am not sure whether I understand that discussion in emacs dev
>> correctly. Will orgmode be moved into the GNU emacs try as it was done
>> with gnus?
> for the record, I would be in favor of this. Wh
Hi Uwe,
Uwe Brauer writes:
> I am not sure whether I understand that discussion in emacs dev
> correctly. Will orgmode be moved into the GNU emacs try as it was done
> with gnus?
for the record, I would be in favor of this. Why?
- Less installation headaches
- Less maintainance and backward-c
>>> "Rasmus" == Rasmus writes:
> Uwe Brauer writes:
>> I am not sure whether I understand that discussion in emacs dev
>> correctly. Will orgmode be moved into the GNU emacs try as it was done
>> with gnus?
> AFAIK, there are no such plans. The *version* of Org shipped with Ema
Uwe Brauer writes:
> I am not sure whether I understand that discussion in emacs dev
> correctly. Will orgmode be moved into the GNU emacs try as it was done
> with gnus?
AFAIK, there are no such plans. The *version* of Org shipped with Emacs
is being updated to v9, though.
But perhaps I misse
Hi
I am not sure whether I understand that discussion in emacs dev
correctly. Will orgmode be moved into the GNU emacs try as it was done
with gnus?
If so, how can I download and test for example the current master
branch.
I didn't mind that policy for gnus, since the development is rather
slow
22 matches
Mail list logo