From: "Eric Schulte" <schulte.eric@gmail.com>
To: Nathan Neff <nathan.neff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Good way to try new org-mode code?
Date: Wed, 30 Jun 2010 14:00:02 -0700 [thread overview]
Message-ID: <87wrtgtewd.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTimnvFdWAnWHUublcOCx0QkhY_KdDNThzixFKy1B@mail.gmail.com> (Nathan Neff's message of "Wed, 30 Jun 2010 15:50:01 -0500")
Hi Nathan,
There are a couple of options here.
If you are only playing around with a couple of functions, or in a
single file, you can interactively evaluate single functions by pressing
C-M-x `eval-defun' with your cursor over the function, similarly you can
interactively evaluate entire files with C-c v `eval-buffer'. In both
of these cases the interactively evaluated functions will take
precedence over anything loaded on startup, so this is a great way to
experiment with new function definitions. As a side note, when you want
to debug a function, or closely track it's execution path you can prefix
the `eval-defun' function above (i.e. with C-u C-M-x) which instrument
the function with edebug (the results of which will become clear next
time to use the function).
As for make issues, it is possible to use Org-mode without ever running
make or make install.
I don't know of a way to forcefully reload all of Org-mode, but I find
that evaluation at the function/buffer level is generally sufficient for
my needs.
Best -- Eric
Nathan Neff <nathan.neff@gmail.com> writes:
> I'm using git to track org-mode, and would like to know if there's a way
> to switch branches / mess with code in org-mode without having to
> run make and make install when I want to test the new code.
>
> Currently, I have org-mode code in my ~/.emacs.d/src/org
> directory, and I add this directory to my load-path in my emacs file:
>
> ;; Add org-mode to path
> (setq load-path (cons "~/.emacs.d/src/org/contrib/lisp" load-path))
> (setq load-path (cons "~/.emacs.d/src/org/lisp" load-path))
>
> If I switch branches, or change some code in the above directory,
> I don't think the new code is used by emacs unless I run
>
> make clean && make && sudo make install
>
> Is there a way to have emacs read the org-mode source code "on the
> fly" without having to run make, make install, etc?
>
> Is there a way to run new code without restarting Emacs?
>
> Thanks,
> --Nate
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-06-30 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 20:50 Good way to try new org-mode code? Nathan Neff
2010-06-30 20:55 ` Erik Iverson
2010-06-30 21:00 ` Eric Schulte [this message]
2010-06-30 21:09 ` Sébastien Vauban
2010-06-30 21:12 ` Bastien
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=87wrtgtewd.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nathan.neff@gmail.com \
/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).