Is a tutorial/guide available for org-notify? Neither of the following were very
helpful:
http://orgmode.org/worg/org-api/org-notify-api.html
http://thread.gmane.org/gmane.emacs.orgmode/52634/focus=52693
Thanks.
Bastien bzg at gnu.org writes:
Can you provide a reproducible recipe?
I'm going to try to make a minimal example. In the previous image, 10 days was
*not* in the upcoming faces face -- it was in default face. However, in this
example:
http://imgur.com/ge0hY
10 days *is* now in the upcoming
I wrote:
snip
http://imgur.com/ge0hY
snip
In the example image above:
1d is in org-upcoming-deadline face
5d is in org-upcoming-deadline face
8d is in default face
10d is in org-upcoming-deadline face
26d is in default face
45d is in default face
*However*, the entry for the 10d line
Bastien bzg at gnu.org writes:
I have agenda TODO items due in 5d (in org-upcoming-deadline face),
in 16d (in default face) and in 26d (in org-upcoming-deadline face).
Why is the 16d deadline in default face?
I can't reproduce this.
Can you provide a recipe and/or a screenshot?
It has
Nick Dokos nicholas.dokos at hp.com writes:
Apparently the (old) latex exporter still shows symptoms of that
disease. Note btw, that the buggy behavior is confined to the old
exporter: the new exporter DTRT with or without the empty line.
I've seen some mention of this new exporter. Where
Bastien bzg at gnu.org writes:
I can't reproduce this.
Can you provide a recipe and/or a screenshot?
The date is different now and that particular combination of deadlines is gone.
When I see it again, I'll take a screenshot. Thanks.
Nick Dokos nicholas.dokos at hp.com writes:
Can't reproduce it here: Org-mode version 7.8.11
(release_7.8.11-107-ga69f4b @ /home/nick/elisp/org-mode/lisp/)
Tried both the old and the new exporter, exporting to ascii, latex
and html of the following file:
...
and I only get the bar tree
Suvayu Ali fatkasuvayu+linux at gmail.com writes:
Have you tried with a minimal setup? It's quite easy. Some instructions
are included in the Org mode manual[1]. It also helps if you provide a
minimal example org file, we like to call that an ECM[2] on the list.
I have already confirmed that
Jambunathan K kjambunathan at gmail.com writes:
I'm using Org-mode version 7.8.11-1
7.8.11-1 is very old. Upgrade and problem will disappear.
From the org-mode download page right now:
Current Version: Org 7.8.11
How is 7.8.11 very old? Which version should I upgrade to?
Suvayu Ali fatkasuvayu+linux at gmail.com writes:
Have you tried with a minimal setup? It's quite easy. Some instructions
are included in the Org mode manual[1]. It also helps if you provide a
minimal example org file, we like to call that an ECM[2] on the list.
If you would like a minimum
Correction to previous post:
This exports all three headlines. Modify as follows:
should read:
This exports all *two* headlines. Modify as follows:
Jambunathan K kjambunathan at gmail.com writes:
How about something in the range of 130+ - say release_7.8.11-135?
Unless there is something related to exporting and possibly
org-export-select-tags, I'm not sure this would help. A search here:
Nick Dokos nicholas.dokos at hp.com writes:
Well, so far nobody else can reproduce it, so the working assumption is
that it is an artifact of either the version you are running or your
configuration. As Suvayu suggests, a minimal org setup[fn:1] would
distinguish between the two. Otherwise,
SW sabrewolfy at gmail.com writes:
I am not familiar with downloading any version other than the
one in my distro's repository or the Debian version from
orgmode.org. I will look into getting a version later than
7.8.11-1, which is what my version is. I tested with the
minimal file before
(1) I extracted the latest tar.gz file downloaded from org-mode.org
(org-mode-9d16365c201201679b190c601c8d32e06530a21a.tar.gz) to /tmp/org-mode.
(2) I loaded Emacs with emacs -Q and then entered:
(setq load-path (cons /tmp/org-mode/lisp load-path))
into the scratch buffer.
(4) I marked it and
Nick Dokos nicholas.dokos at hp.com writes:
What does M-x locate-library RET org-install RET say?
Library is file /usr/share/emacs/23.2/site-lisp/org-mode/org-install.elc
(The latest version download is now different -- it no longer says version N/A
N/A. It now says:
Org-mode version
Jambunathan K kjambunathan at gmail.com writes:
While in your org buffer do a
C-c C-e t
#+TITLE: testing.org
#+AUTHOR:
#+EMAIL:
#+DATE: 2012-07-09 Mon
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
SW sabrewolfy at gmail.com writes:
I have an org-file with many headlines of various levels, but no tags. I
tagged
one top-level headline with :export: and exported to LaTeX with C-c C-e l. The
tagged headline and everything below it was exported, but so was the first
headline
Jambunathan K kjambunathan at gmail.com writes:
Looks fine to me ...
What does that mean? Are you getting the behaviour you are expecting.
What I meant is that the export tags *are* correctly set in the template, so
only the :export: headlines *should* be exported, which, despite that
Nick Dokos nicholas.dokos at hp.com writes:
I can confirm that without the empty line the first subtree gets
exported as well as the (tagged) second one (but not the third one in my
minimal example). That's a bug.
But the minimal example I posted *did* include the initial empty line;
SW sabrewolfy at gmail.com writes:
That was my fault. I recall seeing other blank lines elsewhere in your
example, so I must have deleted them all. Apologies for the confusion.
I personally never have such blank lines in a document, so it was a
force of habit.
Why *did* you start
Jambunathan K kjambunathan at gmail.com writes:
I can duplicate what you say. May be it is a bug...
ps: Text is no text with no whitespaces. All along we have been
focussed on text, when we should actually have been focussed on the
whitespace (or in this curious case, the missing
I have an org-file with many headlines of various levels, but no tags. I tagged
one top-level headline with :export: and exported to LaTeX with C-c C-e l. The
tagged headline and everything below it was exported, but so was the first
headline (and everything below it) in the org file, even though
I have agenda TODO items due in 5d (in org-upcoming-deadline face), in 16d (in
default face) and in 26d (in org-upcoming-deadline face).
Why is the 16d deadline in default face?
Eric S Fraga e.fraga at ucl.ac.uk writes:
A simple solution which keeps your interest in the outline structure at
this stage of the writing is to add the line
#+options: H:3
...
Thanks. That's a useful suggestion.
Apologies if this is a basic question. Org-mode is so huge that it's sometimes
difficult to know where to look. I have several DEADLINE entries set with -99d
advanced warning to ensure they appear on my agenda. Entries due in, for
example, 30 or less days are in a different colour to those due in
Nick Dokos nicholas.dokos at hp.com writes:
Probably org-agenda-deadline-faces: I did C-h v org--deadline TAB TAB ...
and scanned the *Completions* buffer.
Thanks. I did C-h v org-deadline. Didn't know about org--deadline instead of
org-deadline :)
I know I'm bumping a thread from 5 years ago :)
Bastien bzg at altern.org writes:
Gijs Hillenius gijs at hillenius.net writes:
But maybe I should not . But here goes: I plan to start working on
an item by date X - schedule stamp. The item has a deadline, so -
deadline.
For that I use
Nick Dokos nicholas.dokos at hp.com writes:
Interesting: it seems to be a latex bug of some sort, but I haven't had
time to play with it too much yet. I'm trying things like modifying the
tex file slightly and seeing if the empty page(s)/overfull page(s)
persist. So far, it seems that all
Nick Dokos nicholas.dokos at hp.com writes:
Interesting: it seems to be a latex bug of some sort, but I haven't had
time to play with it too much yet. I'm trying things like modifying the
tex file slightly and seeing if the empty page(s)/overfull page(s)
persist. So far, it seems that all
suvayu ali fatkasuvayu+linux at gmail.com writes:
http://orgmode.org/manual/Deadlines-and-scheduling.html#Deadlines-and-scheduling
...
Important: Scheduling an item in Org mode should not be understood in
the same way that we understand scheduling a meeting. Setting a date
for a meeting is
Nick Dokos nicholas.dokos at hp.com writes:
Interesting: it seems to be a latex bug of some sort, but I haven't had
time to play with it too much yet. I'm trying things like modifying the
tex file slightly and seeing if the empty page(s)/overfull page(s)
persist. So far, it seems that all
I'd like to clarify some of the usage of timestamps. Preceeding a timestamp with
DEADLINE or SCHEDULE gives extra functionality in the agenda. Omitting these
keywords produces a normal timestamp which *appears* in the agenda but does not
trigger advanced warning before and does not continue to
.
I'll post details when/if I encounter it again. It's happened in every LaTeX
export I've ever tried, but I'll search for a solution again before posting. I'm
working on a minimal example now to help me understand how it works too :)
Thanks.
SW.
Nick Dokos nicholas.dokos at hp.com writes:
snip
You can do that by customizing the org-export-latex-default-packages-alist
variable: just add the above option (without the square brackets) to the
hyperref package entry.
Thanks. This worked -- the red boxes are no longer displayed.
Eric Fraga e.fraga at ucl.ac.uk writes:
adding the line
#+latex_header: \hypersetup{pdfborder={0,0,0}}
in the org document should be sufficient?
Yes, this works too -- the boxes are invisible now.
In practice, I actually do:
#+latex_header: \hypersetup{colorlinks=true}
which
John Hendy jw.hendy at gmail.com writes:
And red isn't my cup of tea, so I use:
#+LATEX_HEADER: \hypersetup{colorlinks=true,urlcolor=blue}
Thanks, but it's linkcolor not urlcolor for the internal links in the TOC.
I'm working on a large document in org-mode which I export to LaTeX. At present,
the outline/structure of the document has been created, but not much of the
content. The LaTeX export has strange pagination, a blank page and text that
runs off the page. Where can I paste/post this example?
Nick Dokos nicholas.dokos at hp.com writes:
If you don't mind making it public, I'd say go ahead and post the org
file (and any relevant customizations) here.
M-x replace-regex RET \w+ RET Text RET
I replaced all words with Text. Here is the document outline. The breakage
happens from page 3
I'm not familiar enough with Emacs to comment about the performance of overlays,
etc., but I'm surprised that processing *text* can be so CPU intensive.
These days we have games running with millions of pixels and shading or whatever
(some use the GPU of course), and browsers with fancy Flash
I know about *bold*, _underline_, etc. which can be used to highlight text. This
is shown in the text itself and in the export.
Is there any other way to highlight text *within* Emacs? I'm looking for
something similar to how org-mode highlights the TODO word. I would like to, for
example,
I'm preparing an academic document with several chapters. The text will
eventually exist as a LaTeX document. However, I am doing my early planning and
writing directly in an org file, making use of the structure elements (*, **,
***, etc) to provide structure and entering text for the relevant
I was making notes today as follows:
==
* List of important items [0%]
- [ ] Item 1
- This is an important item.
- Remember to do the hokey-pokey.
|---|---|
| A | B |
| C | D |
- [ ] Item 2
- This is not as important.
==
Of
Bernt Hansen bernt at norang.ca writes:
TAB won't indent it but you can use the rectable C-x r o to shift it
right so it is part of the list.
Thanks. That's awesome :)
Nicolas Goaziou n.goaziou at gmail.com writes:
Also, the table can't be indented as part of the list.
It can: just move it in manually. Then it will stay there.
Thanks. I thought any indentation should be avoided, but I think this is a good
solution.
Joost Kremers joostkremers at fastmail.fm writes:
TAB won't indent it but you can use the rectable C-x r o to shift it
right so it is part of the list.
actually, IME, if you select the table and then hit tab, it does indent.
Not for me. The rectable solution is a good one though.
Nick Dokos nicholas.dokos at hp.com writes:
Are you sure? As Joost says, you have to select the table (C-space at
one end and move to the other end; and I think transient-mark-mode must
be in effect - which is on by default in emacs24, but maybe not in
emacs23? - so you should see the table
Pressing S-left/right anywhere on a timestamp decreases/increases it by one day.
Pressing S-down/up on a component of a timestamp decreases/increases it by one
unit of that component.
How can we include an easy and quick way to decrease/increase the timestamp by
one week. I find myself having to
Christian Moe mail at christianmoe.com writes:
C-c . +1w
This updates the timestamp to be one week from *today*. I want to push the
timestamp one week forward from wherever it is.
Christian Moe mail at christianmoe.com writes:
Oops, sorry! Forgot the double-plus.
With point on the timestamp,
C-c . ++1w
Ah, that works. Thanks :)
Nick Dokos nicholas.dokos at hp.com writes:
Should I just bind ``C-u 7 S-right`` and ``C-u 7 S-left``?
I wouldn't bother but I'm not you: if you really want to, you can
define a trivial function
(defun sw-one-week-bump ()
(org-timestamp-up-day 7))
and bind it.
snip
Brian van den Broek brian.van.den.broek at gmail.com writes:
A data point:
I've the same broken info system on the ssame version of CrunchBang.
I really like cb, but there are wrinkles like that. The TODO for
solving that hasn't percolated up my list yet
In the meantime, I've posed it on the
Nick Dokos nicholas.dokos at hp.com writes:
snip
But I saw a message implying that Debian does not consider emacs
documentation free (!?!?), so the info files may be in
emacs23-common-non-dfsg in this case.
Thanks, that's the package :)
FWIW, I think you meant:
(info (emacs) Key Binding
I inserted a link to a file with C-c l, file and then navigated to the file
using autocompletion of the path and file names. Movinvg over that link and
pressing C-c l prompts me with the path to the file. Edits in this path will
not longer support autocompletion now. I have searched both generally
Nick Dokos nicholas.dokos at hp.com writes:
o ``C-c C-l'' is an org-mode keybinding to org-insert-link: it takes the
saved information that org-store-link squirreled away and creates a
link at your current location.
Apologies. Yes, I am inserting a link with ``C-c C-l``, navigating to the
Is it possible to include leading zeros in plains lists:
01. Item 1
02. Item 2
Bastien bzg at gnu.org writes:
SW sabrewolfy at gmail.com writes:
Is it possible to include leading zeros in plains lists:
01. Item 1
02. Item 2
No, sorry.
Ok :) It was just to avoid lists looking out alignment:
8. Fetch the package
9. Open the package
10. Look inside
Bastien bzg at altern.org writes:
I think this is intended. If timestamps were not removed from today's
date, agenda listing items scheduled/timestamped for today would be less
readable.
If the year in the timestamp of +1y repeating items is the current year, it *is*
removed from the
SW sabrewolfy at gmail.com writes:
I have entries such as the following:
*** 2011-01-01 +1y New Year's Day :holiday:
which appear on the agenda on the correct day each year, but they appear as:
File: 2011-01-01 +1y Public Holiday: Freedom Day :holiday
SW sabrewolfy at gmail.com writes:
Apologies -- the above was a copy and paste nightmare between Emacs and
Firemacs. What I meant was the following in an org file:
*** 2011-01-01 +1y New Year's Day :holiday:
and the following appearing on the agenda:
File: 2011-01-01 +1y New
Brian van den Broek brian.van.den.broek at gmail.com writes:
1) I believe org works much more happily if you don't include timestamps in
headlines.
This
*** New Year's Day
2011-01-01 +1y
does *not* include the timestamp in the agenda, yes.
However, timestamps are *not* included in the agenda
SW sabrewolfy at gmail.com writes:
This
*** New Year's Day
2011-01-01 +1y
does *not* include the timestamp in the agenda, yes.
However, timestamps are *not* included in the agenda from other entries which
*do* have timestamps in the headline.
I've tested with repeating timestamps
Nick Dokos nicholas.dokos at hp.com writes:
Indeed - I can reproduce that. It happens in org-agenda-get-timestamps,
in the call to org-agenda-format-item: this function takes a regexp
argument, remove-re, and removes any matches from the string it
produces. The regexp is constructed from the
Brian van den Broek brian.van.den.broek at gmail.com writes:
On 17 Apr 2012 09:39, Brian van den Broek brian.van.den.broek at
gmail.com wrote:
2) I just added a bunch of holidays / days of observation to my system. Your
use case is better accomplished via org-anniversary:
SW sabrewolfy at gmail.com writes:
2) I just added a bunch of holidays / days of observation to my system.
Your use case is better accomplished via org-anniversary:
(org-anniversary 2011 01 01) New Year's Day
Emailing before first coffee is a bad idea. I left out some syntax. See
I have entries such as the following:
*** 2011-01-01 +1y New Year's Day:holiday:
which appear on the agenda on the correct day each year, but they appear as:
File: 2011-01-01 +1y Public Holiday: Freedom Day :holiday:
with the date showing. Other deadline/schedule/plain
I'm exporting a structured document to Latex/PDF. The table of contents contains
hyperlinks for each section which I would like to disable. I tried setting
org-export-latex-href and org-export-latex-hyperref to empty strings, but
this did not help. Thanks.
67 matches
Mail list logo
