From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: [BUG] Inconsistency in src block hiding Date: Sun, 11 Dec 2011 09:04:29 -0700 Message-ID: <874nx782wi.fsf@gmx.com> References: <8739djqfkv.fsf@gmail.com> <87fwhiwwr0.fsf@gmail.com> <87bos6pp1a.fsf@gmail.com> <8739dhnxjs.fsf@gmail.com> <87ipmcxboo.fsf@gmail.com> <87pqgjipu8.fsf@gmail.com> <87y5v6x3lv.fsf@gmail.com> <87fwh86533.fsf@gmail.com> <87ehwbdxk2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:55348) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RZmgR-0001ao-1Q for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 11:55:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RZmgP-0003L7-UR for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 11:55:27 -0500 Received: from mailout-us.gmx.com ([74.208.5.67]:45884) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RZmgP-0003L3-Ms for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 11:55:25 -0500 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Org Mode List , Nicolas Goaziou Bastien writes: > Eric Schulte writes: > >> The attached patch entirely removes the #+name and #+results based >> hiding. Note that the existing "wrap" argument to the ":results" header >> argument will wrap results in a block which allows easy tab-based result >> hiding. >> >> As this is a relatively large change I hesitate to apply it outright, >> although I do agree that it leads to simpler more consistent behavior. >> If general consensus seems to support the application of this patch then >> I will be happy to apply it. > > Has there been any more feedback on this? > > Erik, is it safe to apply the patch or shall we wait more? > I've received no more feedback on this patch. It should be safe as it adds no new code but simply removes some questionable code. I will apply this patch now. Best, -- Eric Schulte http://cs.unm.edu/~eschulte/