From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uwe Brauer Subject: Re: how do you compose mails in Gnus with org-mode Date: Thu, 08 Mar 2018 15:16:09 +0100 Message-ID: <87woym3b6e.fsf@mat.ucm.es> 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: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60375) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1etwLJ-0001oK-2Z for emacs-orgmode@gnu.org; Thu, 08 Mar 2018 09:16:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1etwLF-00018g-Sz for emacs-orgmode@gnu.org; Thu, 08 Mar 2018 09:16:25 -0500 Received: from [195.159.176.226] (port=40451 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1etwLF-000189-MR for emacs-orgmode@gnu.org; Thu, 08 Mar 2018 09:16:21 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1etwJ6-0007Gj-9P for emacs-orgmode@gnu.org; Thu, 08 Mar 2018 15:14:08 +0100 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: emacs-orgmode@gnu.org >>> "Tim" == Tim Cross writes: > 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. Problem with the main branch is that the nice feature for the org tables, namely very wide columns get somehow hidden, is not included....