Hi Eric,
Eric S Fraga e.fr...@ucl.ac.uk writes:
Matt Lundin m...@imapmail.org writes:
Any ideas how I might accomplish similar effects in org-beamer (without
having too hack up the org file with too much LaTeX code)?
The attached (with three different figures...) will do the job although
Previously, when one hit C-c C-c on an item with an intermediate state,
the item would be checked as completed. I.e.,
- [-] Do something
...would become...
- [X] Do something
After the recent changes to org-list, typing C-c C-c on an item with an
intermediate state clears the item:
- [ ] Do
Hello,
Matt Lundin m...@imapmail.org writes:
Previously, when one hit C-c C-c on an item with an intermediate state,
the item would be checked as completed. I.e.,
[...]
Would it be possible to restore the old behavior? A progression from
partial completion to full completion seems the most
* lisp/org-list.el (org-list-in-valid-context-p): renamed from
org-list-in-valid-block-p.
(org-at-item-p,org-list-search-generic): use renamed function.
* lisp/org.el (org-fill-item-nobreak-p): new function.
(org-set-autofill-regexps): modify `fill-nobreak-predicate' to
prevent auto-fill
Hi
--8---cut here---start-8---
* Unmatched #+end-src bug
#+end_src
--8---cut here---end---8---
With the above simple org file, placing the cursor at the end of
#+end_src and hitting return causes emacs to hang.
The bug
Hi,
On Sat, Mar 12, 2011 at 22:26, Martyn Jago martyn.j...@btinternet.com wrote:
--8---cut here---start-8---
* Unmatched #+end-src bug
#+end_src
--8---cut here---end---8---
With the above simple org file, placing the
Hi,
I’ve been working on getting org-mode to automatically clock into an
item’s ancestor when clocking out of that item. The way I have it set
up now, it walks up the tree looking for an item that has a particular
property set. If that property is non-nil, it clocks in; if it’s nil,
it doesn’t.
Hello,
Aankhen aank...@gmail.com writes:
--8---cut here---start-8---
* Unmatched #+end-src bug
#+end_src
--8---cut here---end---8---
With the above simple org file, placing the cursor at the end of
#+end_src and
Hi,
On Sun, Mar 13, 2011 at 01:37, Nicolas n.goaz...@gmail.com wrote:
Aankhen aank...@gmail.com writes:
--8---cut here---start-8---
* Unmatched #+end-src bug
#+end_src
--8---cut here---end---8---
With the above
Hi all,
I've looked everywhere I can think of, but I can't find any info on
if/how it's possible to automatically have overdue tasks highlighted or
somehow set off from other tasks, in a todo style block agenda.
I know about doing that in daily/weekly style agendas, but I was hoping to
be able to
Aankhen aank...@gmail.com writes:
Thanks for the heads-up Aankhen, I had indeed missed the enclosing
infinite loop.
I modified your patch slightly since my test still failed, and made
further tests.
From b55d846b57fc2ebf3c282cb1fbb27becfdd7d4fd Mon Sep 17 00:00:00 2001
From: Martyn Jago
Hi,
Could someone fill me in on your process for clocking in things after
the fact? I've been trying to get into to clocking, but, especially at
home, I don't return to my computer in between every different thing.
Instead, I stop at it when I get a pause and try to fill in what I've
been doing.
Nicolas n.goaz...@gmail.com writes:
Hi
Hello,
Aankhen aank...@gmail.com writes:
--8---cut here---start-8---
* Unmatched #+end-src bug
#+end_src
--8---cut here---end---8---
With the above simple org file, placing
Karl: I put you in the loop for info, because in Texinfo mode I think
that @* is used as an alinea separator similar to \\ in Org mode.
From: monn...@iro.umontreal.ca
To: vincent@hotmail.fr
Date: Wed, 16 Feb 2011 10:02:37 -0500
CC: emacs-orgmode@gnu.org; emacs-de...@gnu.org
Subject: Re:
So I am not sure what 64 bit systems do now or in the future, but
it seems that we need to live with a restriction for now.
Maybe this should be documented somewhere.
- Carsten
Most 64-bit systems use a 64-bit int. All of the 64-bit Linux systems
that I've used use a signed 64-bit int.
Hello,
Martyn Jago martyn.j...@btinternet.com writes:
I've supplied a patch which passes all of my tests, but I will look at
providing additional tests looking at other cases within this loop since
I'm currently in the habit of writing tests anyway.
Your patch has the same weakness as the
Actually, no, because paragraph-separate would cause the whole line
that ends with \\ to be treated as not being part of a paragraph, and
paragraph-start wouldn't be appropriate either. Hence the good
above :-(
[...]
I have implemented the thing locally on my machine. It works well but
Hi Orgers,
One (out of five) of my org agenda files has spontaneously shifted to
lower case. Can anyone give me a clue what might have happened?
Thanks,
Alan
--
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel: 04 2748 6206
On Sun, 13 Mar 2011 17:07:14 +1100
Alan L Tyree alanty...@gmail.com wrote:
Hi Orgers,
One (out of five) of my org agenda files has spontaneously shifted to
lower case. Can anyone give me a clue what might have happened?
Pilot error is what happened. I accidentally hig C-x C-l when I was
Hi everyone,
On 11.3.2011, at 09:31, Bastien wrote:
Hi,
Nick Dokos nicholas.do...@hp.com writes:
So I'd guess raising an exception might be the simplest way to deal with
this. Here's a patch to try out:
This patch has side-effects that Carsten have been recently exploring a
bit.
20 matches
Mail list logo
