emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: ANN: org-sticky-header
Date: Wed, 19 Apr 2017 07:07:22 +0100	[thread overview]
Message-ID: <87wpahylph.fsf@t3610> (raw)
In-Reply-To: <ea4543fad79c4e9687992e41ef77062e@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Adam Porter's message of "Tue, 18 Apr 2017 23:53:24 +0000")

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

On Tuesday, 18 Apr 2017 at 23:53, Adam Porter wrote:
> I was using three spaces, which looked okay on my system, but I'm sure
> it didn't look right on everyone's.  I added an option to configure it
> now.  It would be nice to calculate it automatically somehow, but this
> should be an improvement.

Excellent.  Thank you.

One other minor issue: if there are any inline tasks, the sticky header
shows "END" if there is such an inline task not in the window but
between point and the previous headline.  I think that if point is not
within an inline task, you should be skipping inline tasks (my own
preference) or displaying the headline for the task and not the END
line.

Thanks again,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50, Org release_9.0.5-444-g998576

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2017-04-19 13:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a8497792e3994095a9867e508a90bb3f@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-18  7:21 ` ANN: org-sticky-header Eric S Fraga
2017-04-18 23:53   ` Adam Porter
     [not found]   ` <ea4543fad79c4e9687992e41ef77062e@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-19  6:07     ` Eric S Fraga [this message]
2017-04-19 15:03       ` Carsten Dominik
2017-04-19 16:40         ` Adam Porter
2017-04-19 21:33           ` Adam Porter
     [not found]           ` <7a7a9e1653114a578dcb91186e8a4cab@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-24  6:38             ` Eric S Fraga
2017-04-17 23:41 Adam Porter
2017-04-18  3:28 ` Eric Abrahamsen
2017-04-18 23:10   ` Adam Porter
2017-04-18 13:29 ` Carsten Dominik
2017-04-18 13:51   ` John Kitchin
2017-04-18 13:55     ` Carsten Dominik
     [not found]     ` <2357163c15c549d3a13e923dc7d5f6ea@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-18 17:22       ` Eric S Fraga
2017-04-18 19:16         ` Leslie Watter
2017-04-18 23:09         ` Adam Porter
2017-04-18 23:07     ` Adam Porter
2017-04-18 13:57   ` Kaushal Modi
2017-04-18 23:06   ` Adam Porter
2017-04-19  5:46     ` Carsten Dominik
2017-04-19  5:52       ` Carsten Dominik
2017-04-19  6:11         ` Carsten Dominik
2017-04-19 16:44           ` Adam Porter
2017-04-19 21:33             ` Adam Porter
2017-04-23  0:06               ` Charles C. Berry
2017-04-18 23:51 ` Adam Porter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wpahylph.fsf@t3610 \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).