> (Off topic) I never thanked you for your (video) talk at HLUG, which
> essentially introduced me to org-mode proper (despite having already
> generated 'outline mode' formatted output to benefit from the
> outlining). Your talk blew me away, since I had literally no idea of
> the power of org-mo
Hi Nick,
On Wed, Sep 14, 2011 at 6:55 PM, Nick Dokos wrote:
> * This is a test: \(T^{+}\)
Apart from what Christian said, do you have any comments about $..$
and \(..\) ? I hear conflicting arguments about which is preferred
(e.g. $..$ is a TeX construct where as \(..\) is a LaTeX macro arguing
I'm in the same situation and (lack of) consistence is my main problem.
One thing that helps me is to define in my custom agenda commands one
command that only returns the STARTED tasks (Bernt Hansen's website has
more info about this). In this way I can quickly go back to a task that I
started b
I realize that other people's mileage may and does differ, but
personally, I have long found the amazing functionality,
customizability and hackability of Org-mode an astonishingly effective
tool for PTO (Putting Things Off).
:-)
Christian
On 9/14/11 8:59 PM, Olaf Dietsche wrote:
Hi Alan,
Hi Russell
Russell Adams writes:
[...]
>
> I hope that helps.
>
> Thanks.
>
> --
> Russell Adamsrlad...@adamsinfoserv.com
>
> PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
>
> Finger
Hi all,
I have two related feature requests:
1. The ability to refile based on properties. I have a bunch of items
with a :CATEGORY: entry in their property drawer. I would like such
items always to be refile targets. So I'd like, perhaps, a regexp
for property matching, e.g. "\\`:CA
Hi Alan,
"Alan E. Davis" writes:
> I've been using org-mode for a few years. My agenda is cluttered with tasks
> that are weeks and even months past due. I am "this close" to declaring
> "orgmode bankruptcy" and starting from scratch, except my current setup
> works so well for other things.
I get this error: "Error in post-command-hook: (void-variable
org-ans1)" every time I want to use schedule or deadline. After that,
the error message appear with any command. After some minutes, this
error message disappear and I can use anny command as expected.
This problem happens with both the
On Wed, Sep 14, 2011 at 10:43:28AM -0700, Alan E. Davis wrote:
> I've been using org-mode for a few years. My agenda is cluttered with tasks
> that are weeks and even months past due. I am "this close" to declaring
> "orgmode bankruptcy" and starting from scratch, except my current setup
> works
Aloha Alan,
I found myself in a similar situation a while back and it helped me to
do a weekly review. I base mine on Bernt Hansen's experience:
http://doc.norang.ca/org-mode.html#sec-11-1
Every Monday a task pops up reminding me to complete the weekly review.
Clicking on the task takes me to a
I've been using org-mode for a few years. My agenda is cluttered with tasks
that are weeks and even months past due. I am "this close" to declaring
"orgmode bankruptcy" and starting from scratch, except my current setup
works so well for other things. Might still do that, but I want to ask for
Christian Moe wrote:
> But latex subscripts/superscripts should work in Org even without an
> explicit math environment, and they do for me -- exporting Piter's
> T^{+} gives me
>
> T$^{+}$
>
> as expected. Something in his setup?
>
You are right - sorry about the noise.
Nick
But latex subscripts/superscripts should work in Org even without an
explicit math environment, and they do for me -- exporting Piter's
T^{+} gives me
T$^{+}$
as expected. Something in his setup?
Yours,
Christian
On 9/14/11 6:55 PM, Nick Dokos wrote:
Piter_ wrote:
Hi all. I try to put a
Piter_ wrote:
> Hi all. I try to put a superscript in org-mode in this way: T^{+}. But
> it gets exported in latex as $^{\st{}$. Any idea how to avoid it?
> Thanks.
>
{Super,sub}scripts are latex math constructs - try the following:
--8<---cut here---start-
Hi all. I try to put a superscript in org-mode in this way: T^{+}. But
it gets exported in latex as $^{\st{}$. Any idea how to avoid it?
Thanks.
On Wed, 14 Sep 2011 13:35:19 +0200
Christian Moe wrote:
> Hi,
>
> Try setting the :prepend property:
>
> ("l" "System Log" entry (file+headline "~/Documents/org/computer.org"
> "Log") "* %U %? \n %i\n" :prepend t)
>
> hth,
yes, it helped. Thank you very much,
renato
Bob Qualls writes:
> I would like to add the suggested "Activiation" code to the .emacs file but
> I can't figure out which one it is. I downloaded the
> emacs-23.1-bin-i386.zip file for windows.
When you do C-x C-f to open a file just put in ~/.emacs and hit RET --
Emacs will open the file in
Paul writes:
> # olaf+list.orgm...@olafdietsche.de, Wed, 14 Sep 2011 18:44:07 +1000:
>> paul...@telstra.com writes:
>>
>> > I found myself manually "cleaning" most CAPTURE buffers of whitespace
>> > prior to committing them with C-c C-c. The attached patch adds a new
>> > property :whitespace-c
Hi David
David Maus writes:
> Hi Martyn,
>
> At Sat, 10 Sep 2011 09:09:17 +0100,
> Martyn Jago wrote:
>> I'll do some work on testing against version 23 and 22 and maybe put
>> together a how-to get ERT on those earlier systems (on linux).
>
> Just read this through Org mode's patch tracker[1] a
Hi Sebastien
"Sebastien Vauban"
writes:
> Hi Eric,
>
> Eric Schulte wrote:
>> "Sebastien Vauban" writes:
>>> If there is no value assigned to the code block...
>>> ... there is no an error when exporting:
>>>
>>> #+begin_src text
>>> Debugger entered--Lisp error: (wrong-type-argument consp nil)
Hi,
Try setting the :prepend property:
("l" "System Log" entry (file+headline "~/Documents/org/computer.org"
"Log") "* %U %? \n %i\n" :prepend t)
hth,
Christian
On 9/14/11 12:58 PM, Renato wrote:
Hello, I have a computer.org file with this structure:
* Log
** [2011-09-12 Mon 17:34] update
Nicolas Goaziou writes:
> Eric S Fraga writes:
>
>> but behaviour that I can accept, especially as the easy solution is to
>> simply enclose the equation in a latex block:
>>
>> * equation with leading minus sign
>> The following equation
>> #+begin_latex
>> \begin{equation}
>> \label{eq:t
# olaf+list.orgm...@olafdietsche.de, Wed, 14 Sep 2011 18:44:07 +1000:
> paul...@telstra.com writes:
>
> > I found myself manually "cleaning" most CAPTURE buffers of whitespace
> > prior to committing them with C-c C-c. The attached patch adds a new
> > property :whitespace-cleanup to the org-capt
Eric Abrahamsen ericabrahamsen.net> writes:
>
> Thanks for this hint! I had been advising fill-paragraph, this seems
> like a more comprehensive solution.
What is strange though is that (turn-on-orgstruct++) messes up with the header
separator ("--text follows this line--") when calling M-q (fi
Hello, I have a computer.org file with this structure:
* Log
** [2011-09-12 Mon 17:34] update ...
** [2011-09-07 Wed 18:09] update ...
** TODO [2011-09-04 Sun 20:23] nouveau + pm-suspend -> black tty:bug:
I've been adding entries manually up to now. However I'd like to use
capture to make
paul...@telstra.com writes:
> I found myself manually "cleaning" most CAPTURE buffers of whitespace
> prior to committing them with C-c C-c. The attached patch adds a new
> property :whitespace-cleanup to the org-capture-templates.
Thanks for pointing to whitespace-cleanup, I've done this manual
> If you need really prettier tables you can rely on Table->Autoformat.
I felt some sort of templating mechanism would be useful for odt
tables[1]. To this end, I have pushed some changes which honors ODF-1.2
spec[2].
The attached table-template.org and table-template.odt should serve as
an illu
Hi Luke,
Luke Crook wrote:
> Does org-mode support 'flyspell-prog-mode', in that flyspell should ignore
> everything within #+begin_src and #+end_src blocks?
Maybe have a look at http://comments.gmane.org/gmane.emacs.orgmode/42169, and
report wether the patch is functioning, or must be extended?
Hi Eric,
As said previously, I've been forced to add a default value to many code
blocks I had in my local LOB, which I ingest in my `.emacs' file:
#+begin_src emacs-lisp
(when (try-require 'ob-lob)
(org-babel-lob-ingest "~/emacs/site-lisp/my-local-lob.org"))
#+end_src
Weirdly enough, in the
Hi Eric,
Eric Schulte wrote:
> "Sebastien Vauban" writes:
>> If there is no value assigned to the code block...
>> ... there is no an error when exporting:
>>
>> #+begin_src text
>> Debugger entered--Lisp error: (wrong-type-argument consp nil)
>> setcdr(nil "nil=x")
>> #+end_src
>
> All variabl
Carsten Dominik writes:
> On 13.9.2011, at 11:00, Eric S Fraga wrote:
>
>> Hello,
>>
>> I often export just a sub-tree ("C-c C-e 1 p" say). At the end of the
>> export, my point has moved to the enclosing headline and mark is at the
>> end of the contents of that sub-tree. This is a little ann
Does org-mode support 'flyspell-prog-mode', in that flyspell should ignore
everything within #+begin_src and #+end_src blocks?
Thanks,
-Luke
32 matches
Mail list logo
