Achim Gratz writes:
> Thomas S. Dye writes:
>> However, the package manager doesn't (yet) recognize this package and
>> when I download ob-* packages, org-2015* is also downloaded.
>
> Did you restart Emacs? The package files need not be byte-compiled (and
> shouldn't, IMHO).
No, but when I di
Thomas S. Dye writes:
> However, the package manager doesn't (yet) recognize this package and
> when I download ob-* packages, org-2015* is also downloaded.
Did you restart Emacs? The package files need not be byte-compiled (and
shouldn't, IMHO).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305
Thomas S. Dye writes:
> Achim Gratz writes:
>
>> Thomas S. Dye writes:
>>> Excellent. Thanks! Would it be useful to distribute org-21991231 on
>>> elpa?
>>
>> No, not at all… Unless you want to make sure that noone ever gets an
>> update until the next millenium starts.
>
> No, I don't want
Achim Gratz writes:
> Thomas S. Dye writes:
>> Excellent. Thanks! Would it be useful to distribute org-21991231 on
>> elpa?
>
> No, not at all… Unless you want to make sure that noone ever gets an
> update until the next millenium starts.
No, I don't want that. Thanks for the explanation.
Thomas S. Dye writes:
> Excellent. Thanks! Would it be useful to distribute org-21991231 on
> elpa?
No, not at all… Unless you want to make sure that noone ever gets an
update until the next millenium starts.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofel
Aloha Achim,
Achim Gratz writes:
> Thomas S. Dye writes:
>> I do have a technical question that you or someone else on the list
>> might be able to answer for me. When I downloaded the Babel languages
>> from melpa just now, the elpa version of Org mode was also downloaded
>> and installed, eve
Thomas S. Dye writes:
> I do have a technical question that you or someone else on the list
> might be able to answer for me. When I downloaded the Babel languages
> from melpa just now, the elpa version of Org mode was also downloaded
> and installed, even though I didn't ask for it. Why is this
Suvayu Ali writes:
> Hi Tom,
>
> On Thu, Aug 20, 2015 at 01:56:43PM -1000, Thomas S. Dye wrote:
>>
>> Bastien writes:
>>
>> > Hi Rasmus,
>> >
>> > Rasmus writes:
>> >
>> >> One data point: I can absolutely not be bothered using anything that is
>> >> not at least in contrib.
>> >
>> > Just o
Hi,
>> One data point: I can absolutely not be bothered using anything that is
>> not at least in contrib.
>
> Just out of curiosity: don't you use the Emacs package system at all?
At work I cannot use package.el. At home, the search cost associated with
checking out org-random-mode is higher.
Hi Tom,
On Thu, Aug 20, 2015 at 01:56:43PM -1000, Thomas S. Dye wrote:
>
> Bastien writes:
>
> > Hi Rasmus,
> >
> > Rasmus writes:
> >
> >> One data point: I can absolutely not be bothered using anything that is
> >> not at least in contrib.
> >
> > Just out of curiosity: don't you use the Ema
Bastien writes:
> Hi Rasmus,
>
> Rasmus writes:
>
>> One data point: I can absolutely not be bothered using anything that is
>> not at least in contrib.
>
> Just out of curiosity: don't you use the Emacs package system at all?
>
> I used not to use it, but thanks to recent improvements, I find
Hi Rasmus,
Rasmus writes:
> One data point: I can absolutely not be bothered using anything that is
> not at least in contrib.
Just out of curiosity: don't you use the Emacs package system at all?
I used not to use it, but thanks to recent improvements, I find it
quite good now -- and I would
Bastien writes:
> In the meantime, `org-latex-with-hyperref' will be back in 8.3.2 as
> I don't see why we needed to remove this option too.
Because too many cooks spoil the broth. It's a bad idea to have two
variables controlling the same thing. You can put in nil in template if
you don't wan
Russell Adams writes:
> On Tue, Aug 18, 2015 at 07:36:00PM +0200, Bastien wrote:
>> Hi Scott,
>>
>
>> the main reason why 8.3 was not as "stable" as it should have been is
>> that I've been releasing it too quickly, after having been inactive
>> way too long.
>>
>> It's kind of a miracle that Org
Bastien writes:
> Nicolas Goaziou writes:
>
>> At the bare minimum `org-latex-with-hyperref' should be an obsolete
>> alias for `org-latex-hyperref-template', and the latter should support
>> nil as a possible value.
>
> If you want, please go ahead.
Done.
Regards,
Hi Nicolas,
Nicolas Goaziou writes:
> I disagree. Most bugs reported were introduced months ago. Waiting more
> wouldn't have helped here.
s/quickly/hastily
> `org-latex-hyperref-template' is more general that
> `org-latex-with-hyperref'. Now, we have two variables which can
> contradict each
Hello,
Bastien writes:
> that I've been releasing it too quickly, after having been inactive
> way too long.
I disagree. Most bugs reported were introduced months ago. Waiting more
wouldn't have helped here.
> So all the advice you got is good, but think of 8.3 as a "come back"
> release, with
Hi Russell,
Russell Adams writes:
> Could we reduce the amount of maintenance to the core if we separate
> the rapidly changing plugins to separate projects?
I have a plan to let contrib/* live its own life outside of the core
Org repository. I hope this will encourage a sense of ownership for
On Tue, Aug 18, 2015 at 07:36:00PM +0200, Bastien wrote:
> Hi Scott,
>
> the main reason why 8.3 was not as "stable" as it should have been is
> that I've been releasing it too quickly, after having been inactive
> way too long.
>
> It's kind of a miracle that Org development could continue without
On 08/18/2015 01:36 PM, Bastien wrote:
Hi Scott,
the main reason why 8.3 was not as "stable" as it should have been is
that I've been releasing it too quickly, after having been inactive
way too long.
It's kind of a miracle that Org development could continue without an
active "official" mainta
Bastien writes:
> This is not too late -- can you add a note in etc/ORG-NEWS in maint
> about this change?
Forget about this, I've reintroduced org-latex-with-hyperref.
--
Bastien
Hi Scott,
the main reason why 8.3 was not as "stable" as it should have been is
that I've been releasing it too quickly, after having been inactive
way too long.
It's kind of a miracle that Org development could continue without an
active "official" maintainer for so long, and we owe a lot to Nic
Hi Nicolas,
Nicolas Goaziou writes:
> I'm not sure to understand. What is wrong with setting
> `org-latex-hyperref-template' to the empty string?
>
> This change was introduced in Feb 2014. It is a step forward since we
> move from an opt-in/opt-out to a full customizable template.
>
> I overloo
On 08/13/2015 05:32 AM, Eric S Fraga wrote:
On Wednesday, 12 Aug 2015 at 15:06, Scott Randby wrote:
[...]
If there are no stable releases, then maybe the web site should not
say: "Stable version 8.3.1 (Aug. 2015)." Perhaps "stable" should just
be eliminated from that phrase. Certainly, the use
On Wednesday, 12 Aug 2015 at 15:06, Scott Randby wrote:
[...]
> If there are no stable releases, then maybe the web site should not
> say: "Stable version 8.3.1 (Aug. 2015)." Perhaps "stable" should just
> be eliminated from that phrase. Certainly, the use of "stable"
> confused me.
I guess it's
Scott Randby writes:
> I don't understand what is wrong with keeping
> org-latex-with-hyperref. It is easy enough for me to set the variable
> locally for old files while I can use the default \hypersetup{...} for
> new files. Making org-latex-hyperref-template an empty string means I
> cannot us
On 08/12/2015 01:37 PM, Achim Gratz wrote:
Scott Randby writes:
While I've used Org's development version in the past, I stopped doing
that due to my failure to learn how to use git (no time) and other
issues. Now, I only use the stable releases. But the latest 8.3
release doesn't seem so stable
Scott Randby writes:
> While I've used Org's development version in the past, I stopped doing
> that due to my failure to learn how to use git (no time) and other
> issues. Now, I only use the stable releases. But the latest 8.3
> release doesn't seem so stable to me, so I'd like some clarification
On 08/11/2015 04:56 PM, Rasmus wrote:
Hi,
The definition of a major release is in README_maintainer:
Main releases are made whenever Org is in a state where the feature
set is consistent and we feel that the features that are implemented
is something we want to support in the fut
On 08/12/2015 09:39 AM, Nicolas Goaziou wrote:
Hello,
Scott Randby writes:
When I started using 8.3, I discovered that the behavior of commented
headlines had been changed---a change with which I disagree, a change
I could not find in the release notes, and one which forces me to
alter a huge
Here here. I agree that the new clarified COMMENT vs. :noexport:
functionality makes more sense. And thanks to Nicolas and everyone else for
their amazing work.
On Wed, Aug 12, 2015 at 9:39 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Scott Randby writes:
>
> > When I started using 8.3, I discovered
Hello,
Scott Randby writes:
> When I started using 8.3, I discovered that the behavior of commented
> headlines had been changed---a change with which I disagree, a change
> I could not find in the release notes, and one which forces me to
> alter a huge number of files. It seems I missed the di
Hi,
The definition of a major release is in README_maintainer:
Main releases are made whenever Org is in a state where the feature
set is consistent and we feel that the features that are implemented
is something we want to support in the future.
AFAIK, Org 8.2.10 ships with Emacs 24
On Tue, Aug 11, 2015 at 02:33:18PM -0400, Ista Zahn wrote:
> On Tue, Aug 11, 2015 at 1:18 PM, Scott Randby wrote:
> >
> > I guess what I want to know, and maybe there is no answer, is how long
> > should I wait before upgrading to a stable release?
>
> One strategy is keeping an eye on the mailin
On Tue, Aug 11, 2015 at 1:18 PM, Scott Randby wrote:
> While I've used Org's development version in the past, I stopped doing that
> due to my failure to learn how to use git (no time) and other issues. Now, I
> only use the stable releases. But the latest 8.3 release doesn't seem so
> stable to m
While I've used Org's development version in the past, I stopped doing
that due to my failure to learn how to use git (no time) and other
issues. Now, I only use the stable releases. But the latest 8.3 release
doesn't seem so stable to me, so I'd like some clarification about what
the Org maint
36 matches
Mail list logo
