From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: function for inserting a block Date: Fri, 10 Nov 2017 10:31:57 +0100 Message-ID: <87po8qscmq.fsf@gmx.us> References: <877exghblx.fsf@ericabrahamsen.net> <87r2u1cuwj.fsf@ericabrahamsen.net> <87infdctzq.fsf@ericabrahamsen.net> <87k1zsbizs.fsf@ericabrahamsen.net> <87k1zp4rxj.fsf@ericabrahamsen.net> <871slx4j6p.fsf@ericabrahamsen.net> <87376btslq.fsf@nicolasgoaziou.fr> <87vaj7oyxb.fsf@ericabrahamsen.net> <871sl9ow44.fsf@gnu.org> <87fu9pgfkj.fsf@nicolasgoaziou.fr> <87375ouanr.fsf@gmx.us> <871sl8e76c.fsf@nicolasgoaziou.fr> <87y3nfse6m.fsf@gmx.us> <87tvy3sa7m.fsf@gmx.us> <87bmkbflbc.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35952) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eD5fV-0003mX-5u for emacs-orgmode@gnu.org; Fri, 10 Nov 2017 04:32:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eD5fS-0007lV-2X for emacs-orgmode@gnu.org; Fri, 10 Nov 2017 04:32:09 -0500 Received: from [195.159.176.226] (port=55324 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eD5fR-0007jz-Ry for emacs-orgmode@gnu.org; Fri, 10 Nov 2017 04:32:06 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eD5fH-0008Sq-PN for emacs-orgmode@gnu.org; Fri, 10 Nov 2017 10:31:55 +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 Hi Eric, Eric Abrahamsen writes: >> Also, Eric, it seems that org-structure-template-alist only supports a >> single letter for short-hands (the car of an entry in >> org-structure-template-alist is a char). I used to have blocks like "> expanding to an "abstract" special-block, which I guess isn’t possible >> anymore? > > I hadn't thought of that. Really, all I ever wanted was to wrap things > in blocks... > > I don't see any reason why org-structure-template-alist couldn't go back > to using string keys. Then we could use read-string, and wouldn't have > to have special behavior -- a string that didn't exist in the > alist could just be used literally to make a block. I’d prefer that. For some special blocks, a few characters might makes it more intuitive, e.g. "def" → "definition", "hyp" → "hypothesis" etc. Thanks, Rasmus -- Warning: Everything saved will be lost