From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brady Trainor Subject: New headline after no content (empty headline) Date: Sat, 15 Mar 2014 21:24:57 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43166) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOw5D-0001Dc-JT for emacs-orgmode@gnu.org; Sat, 15 Mar 2014 17:25:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WOw56-0006RT-6F for emacs-orgmode@gnu.org; Sat, 15 Mar 2014 17:25:31 -0400 Received: from plane.gmane.org ([80.91.229.3]:36992) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOw55-0006RN-Vv for emacs-orgmode@gnu.org; Sat, 15 Mar 2014 17:25:24 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WOw54-0004HI-L8 for emacs-orgmode@gnu.org; Sat, 15 Mar 2014 22:25:22 +0100 Received: from 75-149-173-2-Washington.hfc.comcastbusiness.net ([75.149.173.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 15 Mar 2014 22:25:22 +0100 Received: from algebrat by 75-149-173-2-Washington.hfc.comcastbusiness.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 15 Mar 2014 22:25:22 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org I am revisiting a workflow that I have a hard time letting go of, despite it's unintended use in Org-mode. That is, I like to visually separate groups of headlines by simply having a couple of empty headlines. This allows more nimble and simple use-case of manually sorting buildup of headlines by quick and flexible tagging (and easy removal of such), and minimal visual aid of a couple empty headlines. This way, I can so sorting and orienting of tasks without much commitment, allowing me to start the process all over again quickly if I feel I didn't "rotate my space" the right way. My problem is that using the default new headline commands, it removes the whitespace from previous lines, so "* " becomes "*\n* ", instead of my desired "* \n* ". So, I started trying to read the org.el file. I thought I had found the "offending" line, (my L7614,) finding ;; If we insert after content, move there and clean up whitespace (when respect-content (org-end-of-subtree nil t) (skip-chars-backward " \r\n") (and (looking-at "[ \t]+") (replace-match "")) (unless (eobp) (forward-char 1)) (when (looking-at "^\\*") (unless (bobp) (backward-char 1)) (insert "\n"))) I thought to try substituting "[ \t]+" with "[\t]+", and byte compiled the file. But this did not solve. So, I never like to ask a question without having an answer myself, so I learned a little more enough about keyboard macros to generate the following somewhat simple and natural solution (natural in that it uses a similar unused key chord): (fset 'new-starred-line [return ?* ? ]) (global-set-key (kbd "C-M-") 'new-starred-line) So, what is my question? What am I lacking in my .el package reading skills? Why did my first fix not work? As a newb program hacker, am I approaching this right? Maybe best case is to understand more of the entire org.el file, but was trying to hack just enough. What would you have done? Regards, Brady