Rasmus writes:
> Nicolas Goaziou writes:
>> Do you mean KEYWORD and DESCRIPTION should also belong to category 1?
>> I'm not against it, but then, back-ends are required to support them
>> whenever possible.
>
> At the moment they are. They lack ascii support, but at least keywords
> should be
Hello,
Xavier writes:
> I have several org-capture-templates with the clock-in property set to t
> but, either I do not understand how it works either there is a bug but,
> AFAICS, I do not see the clock-in when triggering the template.
Could you send an ECM?
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> It's amazing what an effect barky compiler errors can have.
>
> Thanks. However, `cl-flet' is not supported in Emacs 23 so it's not an
> option for Org 8.3.
>
> OTOH, most uses of `flet' can be replaced with a plain `lambda' and
>
Nick,
thank you very much for your helpful suggestions! After loading ob-lilypond.el,
test-ob-lilypond.el and org-test.el from the git repo 38/42 tests passed. After
I also loaded ob-org.el (git-repo) only one test failed. So I guess my org-mode
version 8.2.7b (installed via elpa) is too old???
Dear Org experts,
I was wondering if anyone could advise on this simple problem.
My toy org file, shown as below, contains 3 projects. I’d like to
export beamer PDFs for individual projects from time to time,
but the pain is that I always need to modify the header options
(title, select_tags
Hi Zhihao,
Zhihao Ding writes:
> Dear Org experts,
>
> I was wondering if anyone could advise on this simple problem.
> My toy org file, shown as below, contains 3 projects. I’d like to
> export beamer PDFs for individual projects from time to time,
> but the pain is that I always need to mod
On Sat, Mar 28, 2015 at 12:26 PM, Rick Frankel wrote:
> On Thu, Mar 26, 2015 at 02:57:40PM +0100, Alan Schmitt wrote:
> > On 2015-03-26 14:50, Bernd Haug writes:
> >
> > I'm using this nice trick (passed to me by a colleague) that sets the
> > environment variables and path to be the same in zsh
Nicolas Goaziou writes:
>> So I would keep them. The documentation explicitly states which backend
>> these keywords are supported by.
>
> OK. Then DESCRIPTION and KEYWORD stay in "ox.el", and documented in
> "Export settings". You need to revert your patch about it.
I thought we were just disc
Thanks Andreas! This is very helpful.
I am using tags to control how verbose I want my export to be
and currently they differ slightly between projects. Quite often
I also have project specific tags. But no problem I think that’s
manageable with the layout you suggested.
Best,
Zhihao
> On
I've modified my config to use IPython.
doesn't work:
src_python[]{return 2+3} {{{results(==)}}}
works w/o 'return':
src_python[:session]{2+3} {{{results(=5=)}}}
doesn't work:
src_python[:session]{return 2+3}
-k.
On 2015-03-30 at 02:41, Richard Stanton wrote:
> :session doesn't seem
I made myself a .emacs snippet with some bindings for using a Logitech
R400 presenter with org-present; maybe some of you can use this, too.
Minor questions noted below.
-
(defun my-on-org-mode ()
(local-set-key (kbd "") 'org-present))
(defun my-on-org-present ()
(org-present-big
Thierry Banel writes:
> Hi Robert
>
> Those #includes were a proposal I did long ago.
> The purpose was to make short scripts even shorter with default
> #includes that everybody uses.
>
> Your use-case is worth considering.
> If this cause trouble, it is easy to remove the includes.
>
> To keep
Hi,
how can I set up an agenda view in org-mode which does NOT show old entries which contain scheduled or deadline dates older than 3 months?
I did not find an option for that - maybe I've overlooked it?
Kind regards
Martin
"Martin Beck" wrote:
> how can I set up an agenda view in org-mode which does NOT show old
> entries which contain scheduled or deadline dates older than 3 months?
> I did not find an option for that - maybe I've overlooked it?
Something like (untested):
(tags-todo "DEADLINE>\"<-3m>\")
Best re
Trying to just read Xavier's email message in Gnus, I get the following
backtrace (with unprintable characters replaced by periods) - to me, this
looks like a bug somewhere, but not sure where:
Debugger entered--Lisp error: (error "Before first headline at position 114 in
buffer *fontification*<2
[Not sure why, but quoting the OP's message did not work - I had to do
it by hand - I wonder if the problem is with the message or my setup:
if someone could verify, I'd appreciate it.]
"Martin Beck" writes:
> how can I set up an agenda view in org-mode which does NOT show old
> entries which co
Hi Nick,
thanks a lot for your help! That looks great, however I don't get it to work:
lightweight example agenda (shows also scheduled items which are >500 days old!):
("y1" "test" agenda "" ((org-agenda-todo-ignore-scheduled -30)))
What am I doing wrong?
I'm still on org-mode
Marco,
Thanks for the suggestion, but this doesn't make the bug go away for me.
Peter.
On Sun, 29 Mar 2015, at 19:54, Marco Wahl wrote:
> Peter Westlake writes:
>
> > On Thu, 26 Mar 2015, at 17:26, J. David Boyd wrote:
> >> Peter Westlake writes:
> >>
> >> > From time to time Org-drill shows
I make pretty extensive use of some custom agenda views to manage and schedule
my workflow.
Lots of todos with timestamps(Deadlines & Schedules).
It's fairly easy shift deadlines back & forth from agenda view using and
There is inconsistency in how this works however.
Deadlines may either simpl
Hi Peter,
Peter Westlake writes:
> Thanks for the suggestion, but this doesn't make the bug go away for
> me.
That's awkward.
Just to be sure: did you evaluate the function after changing the line
in function org-toggle-latex-fragment of org.el to
; (set-window-start nil window-start)
? I
On Mon, 30 Mar 2015, at 17:54, Marco Wahl wrote:
> Hi Peter,
>
> Peter Westlake writes:
>
> > Thanks for the suggestion, but this doesn't make the bug go away for
> > me.
>
> That's awkward.
>
> Just to be sure: did you evaluate the function after changing the line
> in function org-toggle-
Peter Westlake writes:
> On Mon, 30 Mar 2015, at 17:54, Marco Wahl wrote:
>> Hi Peter,
>>
>> Peter Westlake writes:
>>
>> > Thanks for the suggestion, but this doesn't make the bug go away for
>> > me.
>>
>> That's awkward.
>>
>> Just to be sure: did you evaluate the function after changin
> Date: Sun, 29 Mar 2015 23:41:52 -0700
> From: Richard Stanton
> To: emacs-orgmode@gnu.org
> Subject: [O] How to get inline python code to work with :session
> option?
> Message-ID: <438abcf3-a5e3-4743-92de-6b85e3e2e...@haas.berkeley.edu>
> Content-Type: text/plain; charset=us-ascii
>
> :s
elwood...@web.de writes:
> thanks a lot for your help! That looks great, however I don't get it to work:
>
> lightweight example agenda (shows also scheduled items which are >500 days
> old!):
>
> ("y1" "test" agenda "" ((org-agenda-todo-ignore-scheduled -30)))
>
> What am I doing wrong?
>
Ok, 100% of votes are for the removal of wired #includes.
Here is the patch. Tests are changed accordingly.
Thierry
Le 30/03/2015 16:39, Nick Dokos a écrit :
>
> IMO, it would be better than the current situation, but I wonder if
> it makes sense to have a global default setting containing the
I find the option to view logged state changes (via v l or v L) in the agenda
useful. Is there a way to view all notes? I take a lot of notes (via the z
shortcut) and would like to view these too. Is this possible? Or should I just
get in the habit of state changing to the existing state, in wh
Hello,
[sorry for the delay, I had some git SNAFUs]
> Could you also send and updated patch containing the VALUE optional
> argument to `org-re-property' and changing modifying only the (re ...)
> line in `org-find-property', with a new profiling?
Seems like this does trick. I don't really under
27 matches
Mail list logo
