unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>,
	Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: Advice on studying Emacs Lisp files
Date: Wed, 14 Jan 2015 13:59:29 -0800 (PST)	[thread overview]
Message-ID: <fcb6d4b2-e3ec-4ce1-bbb3-f25b4fa92105@default> (raw)
In-Reply-To: <87fvbdhvpv.fsf@wmi.amu.edu.pl>

> so I started a personal project of code reading.  I would like to start
> with (standard) Emacs files.
> 
> However, here's a problem: I'd like to take notes while I'm studying.
> And it's no surprise that I'd like to use Emacs to do this.  For obvious
> reasons, I don't want to make my notes in the files themselves (as
> comments).  OTOH, if I copy them to some personal directory, I lose the
> ability to use find-function (which will jump to the original files).
> 
> Do you have any suggestions for a good workflow for that?  I might use
> Org-mode (and links), but it would involve jumping between buffers,
> which might not be optimal.  Maybe someone has a better idea?

You can bookmark locations, and use annotations for your notes.
If you use Bookmark+ then you can use Org mode for the annotations.



  reply	other threads:[~2015-01-14 21:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 21:57 Advice on studying Emacs Lisp files Marcin Borkowski
2015-01-14 21:59 ` Drew Adams [this message]
2015-01-14 22:22   ` Marcin Borkowski
2015-01-14 23:30     ` Drew Adams
2015-01-17 14:44       ` Marcin Borkowski
2015-01-17 20:32         ` Drew Adams
2015-01-23 23:06           ` Marcin Borkowski
2015-01-23 23:38             ` Drew Adams
2015-01-24 11:57               ` Marcin Borkowski
2015-01-24 15:40                 ` Drew Adams
2015-01-26 22:59                   ` Marcin Borkowski
2015-01-27  0:39                     ` Drew Adams
2015-01-26 23:04               ` Marcin Borkowski
2015-01-27  0:39                 ` Drew Adams
2015-01-28 23:53                   ` Drew Adams

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=fcb6d4b2-e3ec-4ce1-bbb3-f25b4fa92105@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    /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.
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).