emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bill White <billw@wolfram.com>
To: emacs-orgmode@gnu.org
Subject: newbie - gnus links/split windows/breadcrumbs
Date: Tue, 10 Feb 2009 09:02:32 -0600	[thread overview]
Message-ID: <87skmmgws7.fsf@wolfram.com> (raw)

Howdy -

I've finally taken the plunge into org-mode - I'm transferring my last 3
years of old planner/muse notes to org for its better html export and
its astounding rate of development.

So naturally I've found a few little things that bug me:

 - gnus hyperlinks open a new frame, rather than teleporting me to my
   running instance of gnus in the current frame.  Is it possible to
   keep things in one frame?  My gnus links are of the form

[[gnus:nnml:wri.d-wpt#<87y719beqv.fsf@wolfram.com][E-Mail to Joe Schmoe]]

 - C-o on an "external link" to another file in my ~/org results in a
   split window with the target file at the bottom.  Is it possible to
   open targets in the same window?  When I follow a trail of links to
   separate files (homepage -> project homepage with hundreds of
   projects for my manager to read -> details of a single project) I'm
   left with a tiny window and have to do C-x 1 to clean things up.

 - breadcrumbs: http://en.wikipedia.org/wiki/Breadcrumb_(navigation).  A
   link from, say, ~/org/projects.org, to a nonexistent file,
   [[file:blargh.org][blargh]], opens a buffer named blargh.org.
   Immediately after creating the new buffer, would it be possible to
   insert a link that points back to the calling page?  In this example,
   the following link would appear at the top of blargh.org:

Thanks -

Bill White . billw@wolfram.com . http://members.wolfram.com/billw
"No ma'am, we're musicians."

             reply	other threads:[~2009-02-10 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 15:02 Bill White [this message]
2009-02-10 22:36 ` newbie - gnus links/split windows/breadcrumbs Carsten Dominik
2009-02-10 22:40 ` Samuel Wales

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:

  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=87skmmgws7.fsf@wolfram.com \
    --to=billw@wolfram.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).