Thanks!
From: Nick Dokos
To: Christian Prothmann
Cc: Bernt Hansen ; "emacs-orgmode@gnu.org"
; nicholas.do...@hp.com
Sent: Sunday, January 1, 2012 11:01 PM
Subject: Re: [O] Difficulty with repeater timestamps in agenda
Christian Prothm
Thanks Bernt!
From: Bernt Hansen
To: nicholas.do...@hp.com
Cc: Christian Prothmann ; "emacs-orgmode@gnu.org"
Sent: Sunday, January 1, 2012 10:45 PM
Subject: Re: Difficulty with repeater timestamps in agenda
Nick Dokos writes:
> Bernt
- than as a planning
tool. Please let me know if you have any further suggestion or comments. Thanks
again for your quick feedback.
CK
From: Nick Dokos
To: Bernt Hansen
Cc: Christian Prothmann ; "emacs-orgmode@gnu.org"
; nicholas.do...@hp
Hi,
I am relatively new to org-mode (7.8.02). After working with org-mode for
several weeks, I came to realize that none of the repeater timestamps or tasks
(+1d, 1w or +1m) show in the agenda timeline unless there is another
"one-time" timestamp for the same day. Basically, I am not able to
Oh, right, it gets a bit more complicated if you want better control
of the tabulated blocks, i.e. border separation and spacing between
the table cells. Then you first need to wrap them in a . You
could do that with literal HTML, or (my preference) with
org-special-blocks. Use CSS to display t
writing some custom CSS to control how the serial content
is displayed on the page. The "display" css style would be relevant
here.
Yes,
pre.src {display: table-cell;}
will do it in HTML. Full example follows below. I'll leave LaTeX to
those in the know...
hth,
Christian
---
#
I'm forwarding this to the list as it was sent only to my mailbox by
mistake. -- Christian
-
Dear Orgers,
I would like to make a feature request for microsecond timestamps.
Since I often find myself making a list and checking it twice, I think
the excellent Org mode would be a
6. Finaly it is possible to make a table that i use a lot a form that
i can fill and it is possible with i don't know a short-cut or
something to call this form when i need it.
Depending on what exactly you have in mind, Org Capture might be the
answer.
Yours,
Christian
Thanks, now it works.
Yours,
Christian
On 12/21/11 12:24 AM, Dave Marquardt wrote:
Bastien writes:
Hi Dave,
Dave Marquardt writes:
I modified the Makefile to do what I expected. With this change, "make
install" copies the style files to $(prefix)/share/emacs/etc/styles, and
"red-style" -- I assume we'd have to create that style first?
If you look at OrgOdtStyles.xml (C-h v org-odt-styles-dir) and you can
see a bunch of styles marked as "Org Agenda Styles". These are used for
marking TODO in red and DONE in green etc.
Copy& paste those styles, fix the name and background color and you are
done.
Thanks, that's helpful.
Yours,
Christian
ld someone confirm that
etc/styles is automatically installed on Linux / that it isn't on Mac?
Yours,
Christian
ld a
patch for that be considered too much of a corner-case? I'd be happy
to submit one.)
I don't know what others think, but I think the habit of always
providing one's custom links with an explicit fallback should be
encouraged, if necessary by rude reminders from failing exporters...
:-)
hth,
Christian
Of course, getting libreoffice to do what I want is another story... ;-)
I imagine I'll have to use a mouse :-(
Well, you can always author your own styles file in plain XML
conforming to the ODF specification. No mouse required!...
;-)
Christian
running an old bleeding-edge development
version of the ODT exporter.
If you can update to Org 7.8, you should do that; as of this week, the
ODT exporter is part of core Org. (And when you update, clean out old
versions of org-odt from your load-path and your .emacs.)
hope this helps,
Christian
org-export-odt-styles-file to that file as your style template.
hth,
Christian
it be that, because there hasn't been anything to install from
the etc directory before, the Org-mode Makefile doesn't take care of
it? The only reference to "etc/" I've found in the Makefile is in
connection with ELPA, which I don't use.
Yours,
Christian
On
nvironments, I got LaTeX mixed in with the ODT XML...
Yours,
Christian
export to HTML (whether
subtree or the whole document). I can "clear" the HTML export error by
exporting the whole document via LaTeX again.
I'm using Org 7.7 (pulled this morning) on GNU Emacs 23.3.1 on a Mac.
Yours,
Christian
On 12/11/11 6:57 PM, Bastien wrote:
Applied, thanks!
Thanks.
Yours,
Christian
this is wonderful! many thanks to Jambu, Bastien, Christian and
everyone involved.
That would be Jambu, for developing the whole thing, and Bastien, for
integrating it. (I have only done a bit of testing and cheerleading.)
Yours,
Christian
Thanks!
Yours,
Christian
On 12/11/11 2:11 PM, Bastien wrote:
Hi Christian,
Christian Moe writes:
I submitted a patch to this effect a month and a half back.
http://patchwork.newartisans.com/patch/979/
Apart from uncommenting that line, I put in an org-open-par after the div
and
Wonderful!
Yours,
Christian
On 12/10/11 6:22 PM, Bastien wrote:
Dear all,
as the subject says. Please all test this heavily and report
any problems. This will be part of Org 7.8 and soon in Emacs.
Thanks a lot to Jambunathan for all this efforts, let's make
sure everything is smooth b
ultivalued-property. But regexp searches are
fairly simple to use, and work now.
You'll want to think carefully about what you put in properties, what
you put in tags, and what you put in multi-value properties, with a
view to making this easy to search and change as your file grows.
Yours,
Great news!
I'll go over the documentation as promised.
Yours,
Christian
On 12/11/11 12:13 AM, Jambunathan K wrote:
Hello Christian
Christian Moe writes:
Hi,
Great, I'll just wait for your revised draft so we don't get versions
mixed up.
You would have seen this ann
te that doesn't become an opening
curly quote into a closing curly quote, identical to curly apostrophe.
Yours,
Christian
ho said: "'Being' is a surprisingly
difficult concept, but not as hard as 'non-being'"?
#+end_example
It seems like even
single-quote pairs could work well if you put beginning-of-word (\<) and
end-of-word (\<) regex anchors in there.
I've experimented with those anchors, but ended up doing without them;
punctuation mixes with quotation marks in odd ways.
Yours,
Christian
uot; “\\1”")
org-export-html-special-string-regexps))
There may be a better way to do it altogether, and I'm sure the very
simple regexp could be improved on (in fact, I'm posting this in the
hope someone will improve on it), but it mostly works.
Yours,
Christian
Hi,
I submitted a patch to this effect a month and a half back.
http://patchwork.newartisans.com/patch/979/
Apart from uncommenting that line, I put in an org-open-par after the
div and rearranged a few lines to follow the same structure as other
similar bits of code.
Yours,
Christian
On 11/23/11 5:45 PM, Erik L. Arneson wrote:
Thanks, that looks like a good start!
Let me know how it went.
Christian
r creators)))
(setq creators (cdr creators)))
(insert
(format
"
\n"
title fdate description))
(while subjects
(insert
(format "\n"
(car subjects)))
(setq subjects (cdr subjects))
(add-hook 'org-export-html-final-hook 'org-export-with-dc)
#+end_src
Yours,
Christian
Hi, Adam Smith,
You're repeating my misunderstanding -- that's not what he's looking
for, see the thread above.
Christian
On 11/22/11 7:35 PM, adam.smith wrote:
Yes, though it doesn't need to be only COinS. Zotero supports a number
of different formats, but COinS look
the document itself
(author, title, etc.)?
Yours,
Christian
On 11/21/11 10:14 PM, Erik L. Arneson wrote:
I thought zotero-plain was used to add citations. What I'm trying to do
is use org-mode to export HTML files with Zotero-friendly headers that
the Zotero plugin will pick-up on i
e you should get the COinS data.
If that works, zotero-plain could be very easily extended with a
function to insert COinS data for all items in zotero links, and it
could be run as a hook on HTML export.
It hasn't worked for me lately, so I can't try the experiment myself.
Yours,
C
by MODIFIER is multiplied
by the specified number of MINUTES to obtain an effort in
minutes.
For example, if the value of this variable is (("hours" . 60)), then an
effort string "2hours" is equivalent to 120 minutes.
--
Christian Egli
Swiss Library for the Blind, Visually Impa
output verbatim
etc.
Or if you've got everything under the same (parent) heading:
* Top-level heading
:PROPERTIES:
:session: *R*
:cache: yes
:results: output verbatim
:exports: both
:tangle: yes
:END:
hth,
Christian
f this works for you, the code (which is a quickly thrown-together
mess) can probably be improved on.
Yours,
Christian Moe
** OrgMode.js translator
Installation:
1. Tangle or copy the below to a file called "OrgMode.js".
2. Place it in the Zotero translators folder (on Mac, that&#
On 11/13/11 12:45 AM, Christian Moe wrote:
A good while back -- before zotero-plain -- I spent some late nights
Sorry about the noise: I didn't mean to send this fragment. Please ignore.
Christian
On 11/11/11 5:12 PM, Erik Hetzner wrote:
At Fri, 11 Nov 2011 10:51:22 -0500,
Matt Price wrote:
> Wouldn't the rigt target be, not the sqlite db, but the Zoteor*service*
> that runs on port 50001 when Zotero is running? Aren't there some
> higher-level tools for working through that interface
!
Just to be clear, I only used org-bbdb as an example, I wasn't
planning to change it (but what I *was* trying to do with custom links
and ODT was a bit too involved for a minimal example). (And I did not
mean to imply that changing it is your job.)
Yours,
Christian
g intended for HTML:
Here's my own address (Moe).
...which, of course, displays as:
Here's my own address ().
Yours,
Christian
On 11/11/11 10:13 PM, Jambunathan K wrote:
I wonder whether the issue is related to we - Matt(?), Christian(?) and
I - using Windows.
You can scratch that possibility, I'm on a Mac (OS X 10.6.8). It
worked, albeit a little erratically, on my previous (10.5) Mac. That
one was old and
x27;ll try to figure it out.
Yours,
Christian
zotero-plain, MozRepl and
moz.el I could find), I press `C-c z i' to insert a citation and
nothing happens. Well, the Org buffer hangs until I press C-g, and
except that the *MozRepl* buffer says "Process MozRepl deleted".
Yours,
Christian
ot;~/org/contacts.org" "Contact")
"* %?%(org-contacts-template-name) %^g
%(org-contacts-template-email)
%^{URL}p %^{WORK}p %^{HOME}p %^{MOBILE}p
%^{LOCATION}p %^{BIRTHDAY}p %^{NOTE}p")))
...but then you'd be prompted for everything, each time; you may not
want that.
Yours,
Christian
sing the subheading: "* $$ $$" and exporting again.
Getting "$$" as a subheading is not quite straightforward, but the
following will work. Create a user-defined dollar-sign entity (org
doesn't have one by default):
(setq org-entities-user
'(("dollar" "\\$" nil "$" "$" "$" "$")))
Now "* \dollar\dollar" should work.
Yours,
Christian
roduce it. Your
$$
\alpha = \frac{1}{L_{0}} \left( \frac{L_2-L_1}{T_2-T_1} \right)
= \frac{1}{L_0}\frac{\Delta L}{\Delta T}
$$
exports verbatim for me, and is correctly formatted.
Yours,
Christian
that it creates automatic ids based on
the title of the task. The assumption is that you are not that
interested in defining ids. What do you need them for?
> 3) The 'precedes' property is not exported at all
Yes, this is not implemented. Could you use 'depends' instead? And
po
On 11/3/11 8:57 PM, Herbert Sitz wrote:
This is some seriously cool functionality for Org that deserves wider exposure.
Jambunathan's done a great job.
+1
Christian
those expectations.
Yours,
Christian
temize
#+BIND: foo 1
#+BIND: bar 2
Then this:
#+BEGIN_SRC emacs-lisp
(+ foo bar)
#+END_SRC
would tangle to something like:
(let ((org-export-latex-low-levels (guote itemize))
(foo (quote 1))
(bar (quote 2)))
(+ foo bar))
-- which was not the intention.
Yours,
Christian
Hi,
I've signed the FSF papers (assignment 711933).
Bastien, shall I just add myself to the list, or is there more procedure?
Yours,
Christian Moe
think of other useful applications for
cumulative properties, too (conversely, there'll probably be some side
effect that will turn around and bite us at some point, though I can't
think what it would be).
Yours,
Christian
property: var foo=1
#+property: var bar=2
* Heading
:PROPERTIES:
:var: foo=3
:END:
---
Would it result in (("var" . "foo=3 bar=2"))?
Yours,
Christian
change and the potential negative consequences of combining
the property and variable name spaces.
Well, you would know better than me on both scores, so I'll stop
pushing. Thanks for considering it.
Yours,
Christian
can realize it.
| | |
|---+---|
| 2 | |
| 6 | 4 |
| 7 | 5 |
#+TBLFM: @3$2=vmean(@2$1..@3$1::@4$2=vmean(@2$1..@4$1
| | |
|---+-|
| 2 | |
| 6 | 4 |
| 7 | 5 |
| 3 | 4.5 |
| 9 | 5.4 |
#+TBLFM: @3$2..@>$2=vmean(@2$1..@0$1)
hth,
Christian
property (var) by subsequent #+PROPERTY lines are ignored. (Whereas
further assignments to the same property in property drawers further
down an outline tree will `overwrite' assignments higher up.)
Yours,
Christian
might outweigh the risks.
Yours,
Christian
Hi,
Great, I'll just wait for your revised draft so we don't get versions
mixed up.
Yours,
Christian
On 10/28/11 6:19 AM, Jambunathan K wrote:
I will work on your suggestions and circulate a
revised draft shortly.
Once an initial org.texi gets in to the repo, improving it would be a
breeze.
Yes, that fixed it. Thanks!
Yours,
Christian
On 10/27/11 6:13 PM, Carsten Dominik wrote:
This should be fixed now, please verify.
Thanks!
- Carsten
Reproduced. I think this qualifies as a bug.
Yours,
Christian
king forward to trying this out.)
Yours,
Christian
On 10/26/11 8:04 PM, Jambunathan K wrote:
The org-odt.texi and org-odt.pdf are in the parent of this mail. It is
also accessible as attachment at
http://article.gmane.org/gmane.emacs.orgmode/48468
Proof readers invited.
I cast my vote.
Christian
: x, y, z" does that too (then you've two things in one shot --
why not?).
Yes, if my suggestion becomes reality, this could be a useful refinement.
Yours,
Christian
ly applies to the :var passed to a code block;
there may be other property assignments that it would be good to be
able to split over several lines. Also, I can certainly see the
attraction of the analogous #+TBLFM+: -- though I'm fine with the
existing `C-c '' solution for that, and would be equally happy to see
that solution extended to solve your problem.
Yours,
Christian
ot;
my $SVNSTATENUM = 13;
my $DISP_PACKAGE = "seedDisp_0.4-13.tar.gz";
my $somelocalvar = "something or other";
while(...) {
...
}
---
OK, hopefully my idea is clear by now.
Could it be made to work?
Would it solve some problems?
Would it mess other things up even worse?
Yours,
Christian
different src blocks in
different languages, I don't have any elegant solution.
Yours,
Christian
Hi,
Yes, that works nicely, and should solve Rainer's problem.
I haven't been able to think of anything else that can't be handled by
properties.
And I do think it's a good idea to winnow down the syntax a bit, even
if things break. I just like to grumble.
:-)
Yours,
Ch
- correct?
That's my understanding. And #+PROPERTY offers equivalent
functionality in almost every way, but not, as far as I can
understand, in this corner case.
Christian
On 10/21/11 11:12 AM, Rainer M Krug wrote:
On Fri, Oct 21, 2011 at 10:14 AM, Christian Moe mailto:m...@christianmoe.com>> wrote:
(...)
2. Allowing you to pass multiple buffer-wide arguments with :var.
This could make a substantive difference in some applications. The
fol
oid-variable
org-agenda-move-date-from-past-immediately-to-today)
org-agenda-date-later(1)
org-agenda-do-date-later(nil)
call-interactively(org-agenda-do-date-later nil nil)
Thanks
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zür
that is)
- Write an exporter. For simple ascii exporter that should be doable.
There are however different competing starting points. There is an
experimental generic exporter by Bastien and there is apparently one
by Jambunathan. Can't tell you which one is better.
Hope that helps
--
Chri
arguments through the SRCNAME). E.g.:
#+PROPERTY: var euro=1.3791, salestax=.15
I think I'd like this better in any case.
Yours,
Christian
On 10/21/11 9:28 AM, Sebastien Vauban wrote:
Multiple lines may be used to specify multiple properties. e.g.,
#+PROPERTY: results silent
#+PROPERTY: cach
I disagree with Tom on [1]: it should clearly be "srcname", in analogy
to #+tblname - and also so I don't have to change my files :-} (but see
my question about tblname below).
I'll have to change my files, either way. The price one pays for
inconsistency. But as I've recently learned from Ca
: drawer, as provided in the manual?
Yours,
Christian
(lamenting the demise of the #+BABEL header I'd just recently started
to use)
On 10/20/11 10:12 PM, Eric Schulte wrote:
Nick Dokos writes:
Eric Schulte wrote:
I have just pushed up a change to the Org-mode git repository which
re
their hands with a GUI, when we use ODT we can
reasonably be expected to open up an office application now and again
to modify our templates.
Okay, #+END_RANT...
Yours,
Christian
On 10/19/11 7:54 PM, Jambunathan K wrote:
#+ODT_STYLES_FILE: "/path/to/styles.xml"
Perfect. Thanks for the quick response!
Yours,
Christian
st go ahead and use it.
Yours,
Christian
org-odt exporter has done its job if everything you
could reasonably want to style is exported in a named paragraph or
character style that you can apply a template to.
Yours,
Christian
PS. Mehul, I do have a stopgap solution for specifying the style
template on a per-file basis. Place this s
ll
-- everything's in the Default style.
(...)
I have pushed a fix for this moment ago. Hope things are OK with your
setup.
Yes, whatever the problem was, it's gone now. Thanks!
Yours,
Christian
Hi,
The Org manual (2.5 Structure editing) says to use M-S-
(org-demote-subtree) for what the submitter wants to do.
Yours,
Christian
On 10/18/11 10:55 AM, Sébastien Delafond wrote:
Hello,
from Debian bug #645360 (http://bugs.debian.org/645360):
Here's my test file, call it &
ult style.
This is how I understand the manual, and the thread I referenced
before, and I remember having tested it before at some point when it
worked perfectly, so I'm rubbing my eyes and wondering if it's just
me. Could I ask someone to please check?
Yours,
Christian
On 10/17/1
numbering with
Tools > Outline Numbering. For each of the three heading levels that
are numbered, you need to set Number to None, and delete the dot in
Separator After.
Yours,
Christian
On 10/17/11 4:07 PM, Mehul Sanghvi wrote:
I have the following in my org file:
#+OPTIONS: toc:nil H
In the #+OPTIONS line, set toc:nil
http://orgmode.org/manual/Export-options.html#Export-options
Hope this helps,
Christian
71:17:Warning: assignment to free variable
`org-table-coordinate-overlays'
org.el:18172:54:Warning: `t' called as a function
org.el:18177:71:Error: Invalid read syntax: ")"
Yours,
Christian
Correct html export of todo keywords
* org-html.el (org-export-as-html): Apply
org-export-html-get-todo-kwd-class-name to the the class attribute
of the todo-keyword span tag, not to its text content
The problem was that special characters in todo keywords were being
replaced by underscor
'm posting a patch.
Yours,
Christian
your example buffer, what does `C-h v
buffer-file-coding-system' say?
Yours,
Christian
On 10/14/11 5:47 PM, Arne Babenhauserheide wrote:
Hi,
I started using ✔ and ❢ as replacement for DONE und TODO and I realized that
they get replaced by an underscore (_) in HTML output. Since I r
Hi,
Not sure I can help; I don't quite see how this error could be caused
by anything in the code I sent you. Is this happening on the same
system as you used before? What version of Emacs are you on when this
happens?
Yours,
Christian
On 10/13/11 1:40 PM, Gez wrote:
Thanks. I got
utline,
the prompt for a property key offers completion on all the keys stored
in :Stored_outlines:. See how this works for you.
Yours,
Christian
#+BEGIN_SRC emacs-lisp
(defun cm/org-store-outline-order (arg prop)
"Store the heading order of the subtree of the entry at point
by set
s case is surrounded by a #+BEGIN_SRC block, if
you copy it into an Org buffer, you can also evaluate it simply by
`C-c C-c' with point anywhere on the code block.
- You can change the name and drop the `cm/' prefix if you like (I
just use it as a reminder this is my hack, not part of Org-mode)
e than one level at a time, but might that be a bit much in
terms of affecting performance?
Solved; the below counts the total number of headings first, then
adjusts the zero padding accordingly. Code follows.
Yours,
Christian
#+begin_src emacs-lisp
(defun cm/org-store-outline-order (arg prop)
one... but I won't spoil Marcelo's fun if he wants to write his
own; it was indeed a nice task!
:)
Christian
e RTF export has been quirky for me in the past.)
Cheers,
Christian
On 10/9/11 11:06 PM, Marcelo de Moraes Serpa wrote:
Hi list,
I've seen a designer friend layout a book in InDesign so quickly and
the output is amazing. I wonder if there's a way to feed text into
InDesign documents t
Hi, Torsten,
Incidentally, I had to remove \end{scope} (there is no corresponding
\begin{scope}) to make your code example work. Could that be causing
some of your trouble?
Yours,
Christian
On 10/8/11 4:45 PM, Torsten Wagner wrote:
Hi Eric
``:results output silent'' should sup
PS. Note that with the code example I sent, your templates can also
access the special properties listed in section 7.2 of the manual,
such as TODO, ALLTAGS, TIMESTAMP, DEADLINE etc.
sponding so
quickly to my question.
Pass it forward!
Yours,
Christian
#+begin_src emacs-lisp
(defun cm/org-merge (target)
"Fill a template headlined TARGET with the properties of the
entry at point, replacing e.g. `[AGE]' with the contents of
an :AGE: property. Use `[H
prompt.
To improve on that, how do you want to use it?
Once Fido's data are merged with the template, what do you want to do
with the results? Mail them to someone? Export them to HTML? Make a
new Org entry with the contents and file it somewhere?
Yours,
Christian
On 10/6/11 11:35 AM
tting code into org-html.el
and org-latex.el respectively, together with the handling of
blockquotes, verses, centering etc.
Yours,
Christian
On 10/4/11 11:33 PM, Carsten Dominik wrote:
Hi Christian,
for now I have reverted the patch. WOuld you like to work on a better one?
- Carsten
On 4.1
* org-special-blocks.el
(org-special-blocks-convert-html-special-cookies): Close paragraph
before opening or closing the , and open paragraph after. Also
changed newline placement to be the same as for other blocks.
The problem was that special blocks did not produce well-formed HTML
because they
(and thence to paper): see the org Makefile.
Well, back in the olden days the documentation was simple plain text
inside of org.el which I eventually converted into a texinfo file.
Texinfo has some very nice features which at the time org-mode did not
even dream of having (it did not have an agen
601 - 700 of 1150 matches
Mail list logo
