From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Cross Subject: Re: how do you compose mails in Gnus with org-mode Date: Thu, 8 Mar 2018 22:48:55 +1100 Message-ID: References: <87inafvrwi.fsf@gmail.com> <878tb9bcde.fsf@gmail.com> <87r2oxpl6y.fsf@mat.ucm.es> <87po4hrrj9.fsf@gmail.com> <87lgf581vu.fsf@mat.ucm.es> <87a7vlro6f.fsf@gmail.com> <87zi3kqkbp.fsf@mat.ucm.es> <87k1un1tjb.fsf@gmail.com> <876067ueqe.fsf@mat.ucm.es> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a11479bccb023160566e542e2" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47306) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1etu2c-0008CX-0f for emacs-orgmode@gnu.org; Thu, 08 Mar 2018 06:48:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1etu2a-0000Xq-TR for emacs-orgmode@gnu.org; Thu, 08 Mar 2018 06:48:58 -0500 Received: from mail-qk0-x22c.google.com ([2607:f8b0:400d:c09::22c]:35321) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1etu2a-0000XR-NC for emacs-orgmode@gnu.org; Thu, 08 Mar 2018 06:48:56 -0500 Received: by mail-qk0-x22c.google.com with SMTP id s188so6441366qkb.2 for ; Thu, 08 Mar 2018 03:48:56 -0800 (PST) In-Reply-To: <876067ueqe.fsf@mat.ucm.es> 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: Org-mode --001a11479bccb023160566e542e2 Content-Type: text/plain; charset="UTF-8" Yes, you need to checkout the 26 branch to get the next version to be released. A git branch -a will probably list all the branches and you should see one labelled 26 (I'm not running emacs from git at present, so cannot check). I believe git 26 has been in 'feature freeze' for a while while they try to sort out the main bugs needing to be fixed before 26.1 can be released. Note also that I believe the template changes in org are not in the maint branch, only master. So you could try the maint btranch as that would at least have known bugs fixed. On 8 March 2018 at 19:57, Uwe Brauer wrote: > > > Uwe Brauer writes: > > > To avoid confusion, the official release is still 25.3. The next > > release, which is probably still a ways off, will be 26.1 > > Thanks for the clarification. But in order to compile 26, I would need > to checkout the 26 from the git repo? Do I understand that correctly? > > > > The 27 version is really bleeding edge, containing changes which > > are considered too risky for the next release. I'm not sure how > > frequently bug fixes for 26.1 are merged into the development > > branch. > > Well I started to use that version at a time a specific BIDI function > was only in master but not in the official release. Later a similar > thing occurred with vc.el. > > > From a previous post, I think you mentioned you were running from > > git master from mid/late last year. If your running from git > > master, I think you need to pull fairly regularly as bugs are > > frequently fixed and you could be tripping over something which has > > already been addressed. > > Ah no. I am running emacs git master from end of January. I am running > the git/master version of org mode from last june. Why? Well Nic put in > some very useful stuff in org-table (not in the official release now), > but then later in September/October the whole template engine was > changed in master and I could not find out you to make it work again, > that is why I stick to that very particular org version. > > > I suspect you are likely to run into a number of bugs with the > > latest development version of emacs and you are probably one of the > > very few who are looking at bugs in that version. Good luck. > > > Yeah maybe. At least this way reporting them I could contribute a bit to > GNU emacs. :-D > > > > -- regards, Tim -- Tim Cross --001a11479bccb023160566e542e2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, you need to checkout the 26 branch to get the next ve= rsion to be released. A git branch -a will probably list all the branches a= nd you should see one labelled 26 (I'm not running emacs from git at pr= esent, so cannot check). I believe git 26 has been in 'feature freeze&#= 39; for a while while they try to sort out the main bugs needing to be fixe= d before 26.1 can be released.=C2=A0

Note also that I be= lieve the template changes in org are not in the maint branch, only master.= So you could try=C2=A0 the maint btranch as that would at least have known= bugs fixed.=C2=A0

On 8 March 2018 at 19:57, Uwe Brauer <oub@mat.ucm.es> wrote:

=C2=A0 =C2=A0> Uwe Brauer <oub@mat.= ucm.es> writes:

=C2=A0 =C2=A0> To avoid confusion, the official release is still 25.3. T= he next
=C2=A0 =C2=A0> release, which is probably still a ways off, will be 26.1=

Thanks for the clarification. But in order to compile 26, I would ne= ed
to checkout the 26 from the git repo? Do I understand that correctly?


=C2=A0 =C2=A0> The 27 version is really bleeding edge, containing change= s which
=C2=A0 =C2=A0> are considered too risky for the next release. I'm no= t sure how
=C2=A0 =C2=A0> frequently bug fixes for 26.1 are merged into the develop= ment
=C2=A0 =C2=A0> branch.

Well I started to use that version at a time a specific BIDI functio= n
was only in master but not in the official release. Later a similar
thing occurred with vc.el.

=C2=A0 =C2=A0> From a previous post, I think you mentioned you were runn= ing from
=C2=A0 =C2=A0> git master from mid/late last year. If your running from = git
=C2=A0 =C2=A0> master, I think you need to pull fairly regularly as bugs= are
=C2=A0 =C2=A0> frequently fixed and you could be tripping over something= which has
=C2=A0 =C2=A0> already been addressed.

Ah no. I am running emacs git master from end of January. I am runni= ng
the git/master version of org mode from last june. Why? Well Nic put in
some very useful stuff in org-table (not in the official release now),
but then later in September/October the whole template engine was
changed in master and I could not find out you to make it work again,
that is why I stick to that very particular org version.

=C2=A0 =C2=A0> I suspect you are likely to run into a number of bugs wit= h the
=C2=A0 =C2=A0> latest development version of emacs and you are probably = one of the
=C2=A0 =C2=A0> very few who are looking at bugs in that version. Good lu= ck.


Yeah maybe. At least this way reporting them I could contribute a bi= t to
GNU emacs. :-D






--
regards,

Tim

--
T= im Cross

--001a11479bccb023160566e542e2--