Jan Böcker writes:
> On 20.01.2010 06:22, Richard Riley wrote:
>>
>> I believe I now have a repo set up that can be pulled from. Not sure if
>> its done the correct way since I didnt clone org-mode. Rather I pushed
>> my clone master and then the overrun branch. I *think* that should be
>> ok.
>
On 20.01.2010 06:22, Richard Riley wrote:
>
> I believe I now have a repo set up that can be pulled from. Not sure if
> its done the correct way since I didnt clone org-mode. Rather I pushed
> my clone master and then the overrun branch. I *think* that should be
> ok.
>
> Anyway, the URL is
>
>
I believe I now have a repo set up that can be pulled from. Not sure if
its done the correct way since I didnt clone org-mode. Rather I pushed
my clone master and then the overrun branch. I *think* that should be
ok.
Anyway, the URL is
http://repo.or.cz/w/rgr-org-mode.git
and the branch with pa
This small patch (be gentle, its my first) adds a new
face,org-mode-line-clock-overrun, for the modeline task clock when a
task has overrun its allotted Estimate.
I will try to set up the remote repo thing described here
http://orgmode.org/worg/org-contribute.php#sec-3 but I'm not 100% sure
of wh
I would like to be able to execute arbitrary elisp when I clock in or
out of a certain org.item This would be very, very useful for defining
variables or even keystrokes on a "per project" basis. Ideally it would
work using inheritance so if an item does not have something then the
project or file
Richard Riley writes:
> Which brings up my next query : when does org reread tags? I added a
> filetag (#+FILETAGS) to an open org file and saved it but the agenda
> match did not find it. How can I force a refresh of the tags buffer when
> I save a file?
You can type C-c C-c on the #+FILETAGS
Carsten Dominik writes:
> Hi Jeffrey,
>
> indeed you need to make sure that this hook runs only in Org-mode files.
> This is automatically done by calling
>
> (org-crypt-use-before-save-magic)
>
> after loading org-crypt.el.
>
> Internally, this achieves it's goal by installing
> a function into
Thank you all for these great answers.
God Bless.
- Joe
On Tue, Jan 19, 2010 at 9:57 AM, Carsten Dominik
wrote:
> Hi Joe,
>
> as an alternative to the solution proposed by Jan (turning off
> footnote support entirely), you might also consider marking
> that snippet as verbatim code, for example
> On Tue, 19 Jan 2010 16:03:17 +0100, Carsten Dominik
> said:
> Most likely, when you start Emacs, you have something in your config
> that will load org.el *before* you have added path of Org-mode's
> git distribution to the load path. Then you add to the
> load-path variable, so when
Hi,
is it possible to change how hyperlinks are exported to LaTex without
going into to org-latex.el, but setting by a variable or similar in my
.emacs file?
I would like to export hyperlinks in Latex as \myhref (or something
else) instead of \href, so that I can redefine \myhref using \href
Hi Jeffrey,
indeed you need to make sure that this hook runs only in Org-mode files.
This is automatically done by calling
(org-crypt-use-before-save-magic)
after loading org-crypt.el.
Internally, this achieves it's goal by installing
a function into `org-mode-hook', which will then install
a
On Jan 19, 2010, at 12:16 AM, Xiao-Yong Jin wrote:
Hi, I am trying the new emacs develop version in trunk. I
build org-mode from git as usual. But I just realized I am
actually using the org-mode bundled with emacs instead of
the version I installed from git. My configuration files
are the s
Hi Joe,
as an alternative to the solution proposed by Jan (turning off
footnote support entirely), you might also consider marking
that snippet as verbatim code, for example
* Tips
** Average bytes transferred
: perl -lane'$n+=$F[9]; ++$i; END{print $n/$i}' logfile
or maybe
* Tip
"Alan E. Davis" writes:
> In one large file, I would like to keep a large number of individual
> subtrees, each for independent export to LaTeX.
> Is it possible to isolate the extra parameters needed for a subtree
> isolated from the rest of the file?
Answer:
* procedure 3
:PROPERTIES:
In one large file, I would like to keep a large number of individual
subtrees, each for independent export to LaTeX. Is it possible to isolate
the extra parameters needed for a subtree isolated from the rest of the
file?
For example:
* Handouts
** Plants
#+TITLE: 125 General Principles of Plant R
15 matches
Mail list logo
