From: Cassio Koshikumo <ckoshikumo@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Matt Lundin <mdl@imapmail.org>,
emacs-orgmode@gnu.org,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Synopsis view - moving trees around based on a synopsis
Date: Sun, 12 Dec 2010 22:33:53 -0200 [thread overview]
Message-ID: <AANLkTi=owupGzw=m535A=TyJqePyirBoRJg6ULx=xnuE@mail.gmail.com> (raw)
In-Reply-To: <877hfe28qt.fsf@ucl.ac.uk>
Oh, I definitely think you should keep the ellipsis if you like them;
that was only a suggestion. I'm working without them for a while and
it's really not that bad, at least for me. But the idea of using
unicode glyphs is nice. Gonna try it.
Now, an update: after playing with the function a little more, I came
to a new version. Its behavior is a bit different: it'll only show the
synopsis of VISIBLE subtrees. That's useful because now you can use
the synopsis view on a sparse tree; before, it would go to Contents
view automatically. (So, to replicate the old behavior, you just need
to go to Contents view with S-TAB before entering synopsis view).
Again, if anyone knows how to improve it, please leave a note.
(defun k-synopsis-view ()
(interactive)
(save-excursion
(goto-char (point-min))
(while (outline-next-heading)
(when (not (org-invisible-p))
(hide-entry)
(let ((end (save-excursion (outline-next-heading) (point))))
(when (re-search-forward "\\(^[ \t]*:SYNOPSIS:[. \t]*$\\)" end t)
(org-flag-drawer nil)
(re-search-forward "^[ \t]*:END:[ \t]*" nil t)
(outline-flag-region (match-beginning 0) (match-end 0) t)
))))
))
2010/12/12 Eric S Fraga <e.fraga@ucl.ac.uk>:
> Cassio Koshikumo <ckoshikumo@gmail.com> writes:
>
>
> [...]
>
>> 3. For even better results, I recommend setting org-ellipsis to " ":
>>
>> (setq org-ellipsis " ")
>
> You may wish to set this to something still conveys the hiding of text
> but which may look a little less "dirty", as you say. Maybe something
> like " ▷" (space followed by unicode character #x25b7, also known as a
> white right-pointing triangle)? This works quite nicely for me. I
> would find having a blank alone scary or, at best, confusing?
>
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
> : using Org-mode version 7.4 (release_7.4.10.g93135f)
>
--
Cássio Koshikumo
next prev parent reply other threads:[~2010-12-13 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 6:56 Synopsis view - moving trees around based on a synopsis Cassio Koshikumo
2010-12-12 17:36 ` Eric S Fraga
2010-12-13 0:33 ` Cassio Koshikumo [this message]
2011-01-02 14:52 ` David Maus
2011-01-05 17:21 ` Cassio Koshikumo
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='AANLkTi=owupGzw=m535A=TyJqePyirBoRJg6ULx=xnuE@mail.gmail.com' \
--to=ckoshikumo@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).