Hi,
is there a away to change the color of table lines seperately from the
table content? I found the Org Table face through the customize
interface, but that seems to operate on the entire table.
The background to this question is that I find the default table
presentation somewhat busy
Hi,
I have the following code block in my org file:
#+begin_src ledger :results raw :cmdline ...
!include /Users/he-sk/org/files/finanzen/2011.ledger
#+end_src
If I evaluate this code block I get an error message: Code block
produced no output.
This used to work as of 6 weeks ago. The
Carsten Dominik wrote:
2. Moving through time does not work in a block view when the cursor is in
the TODO list.
Maybe we can find ways to address these two issues? For example, including a
built-in command
for this double view, or seeding org-agenda-custom-commands with this
Hi,
This works on Bash (tested on 4.2.10) and should be easy to remember:
emacs --eval (find-file \/home/somefile.org\ )
Cheers,
Viktor
Achim Gratz wrote:
Bash needs this instead
emacs --eval ( find-file ''/home/somefile.org'' )
THere may be other solutions for bash, but I never
IHMO, this model has two problems:
- There's no way (AFAIK) to reschedule a simple timestamp from the
agenda. You have to hit RET on the entry to visit the org file and
then you can change the date with C-c !.
- Sometimes I want to do some follow-up work after a meeting but I'm too
busy
Hi Sebastien,
Sebastien Vauban wrote:
Viktor Rosenfeld wrote:
- There's no way (AFAIK) to reschedule a simple timestamp from the
agenda. You have to hit RET on the entry to visit the org file and
then you can change the date with C-c !.
You can do C-c C-s from the agenda directly
Hi everybody,
so far I've only used one org file, but it's getting unwieldy and I've
decided to split it up.
I'd also like to split up my attachment directory to reduce clutter.
For example, if I have two org files personal.org and work.org I
would like attachments to go into automatically
At Wed, 21 Sep 2011 11:49:39 +0200,
Viktor Rosenfeld listuse...@googlemail.com wrote:
Hi everybody,
so far I've only used one org file, but it's getting unwieldy and I've
decided to split it up.
I'd also like to split up my attachment directory to reduce clutter.
For example, if I
add-file-local-variable to add a new local
variable. Notice how this function put the local variables at the end of
the file.
--
Darlan Cavalcante Moreira
At Wed, 21 Sep 2011 20:29:25 +0200,
Viktor Rosenfeld listuse...@googlemail.com wrote:
Hi,
this works for simple files
Hi everybody,
in http://thread.gmane.org/gmane.emacs.orgmode/47043 I've posted two
examples of local file definitions at the top of an org file which are
silently ignored for seemingly unrelated parts in the org file. The
definitions work if they are put at the end of the org file.
This
the function add-file-local-variable to add a new local
variable. Notice how this function put the local variables at the end of
the file.
--
Darlan Cavalcante Moreira
At Wed, 21 Sep 2011 20:29:25 +0200,
Viktor Rosenfeld listuse...@googlemail.com wrote:
Hi,
this works
Never mind, Nick Dokos explained the behavior here:
http://thread.gmane.org/gmane.emacs.orgmode/47043/focus=47091
Cheers,
Viktor
Viktor Rosenfeld wrote:
Hi everybody,
in http://thread.gmane.org/gmane.emacs.orgmode/47043 I've posted two
examples of local file definitions at the top
Hi,
is it possible to quickly limit what the agenda is showing to one
category? Basically I'm looking for the functionality offered by
org-agenda-filter-by-tag but with categories. I tried CATEGORY=\some
category\ (and variations with/without (escaped) quotes), but that
didn't work either.
Hi,
org-todo-yesterday and org-agenda-todo-yesterday log a note using the
current timestamp and not a timestamp of 23:59 of yesterday's date.
I'm using Org-Mode 7.7 pulled today from the git repository.
Cheers,
Viktor
Hi,
is it possible to export an org file from the command line, so that a
currently running Emacs instance is not disturbed? I want to export the
attached org file and run the included source blocks, so I have an
activity report in the end. I use the shell script pasted below, but
there are two
Hi,
Sebastien Vauban wrote:
#+BABEL: :engine msosql :cmdline -S SERVER -U USER -P PASS -d
DATABASE -n -w 700
Where is the :engine directive documented?
Cheers,
Viktor
Cool, thanks!
Nick Dokos wrote:
Viktor Rosenfeld listuse...@googlemail.com wrote:
Hi,
Sebastien Vauban wrote:
#+BABEL: :engine msosql :cmdline -S SERVER -U USER -P PASS -d
DATABASE -n -w 700
Where is the :engine directive documented?
The only place I know
Hi,
Jambunathan K wrote:
C-h v org-export-run-in-background
This only works for org-export, but not for org-export-as-XXX.
Additionally, it appears that setting org-confirm-babel-evaluate locally
does not have an effect on background exports. Even setting it globally
in a running Emacs
Hi Nick,
Nick Dokos wrote:
The usual method is to run a separate emacs in batch mode: that will avoid
any conflicts
with the running instance. But batch implies -q, so you will have to provide
a minimal .emacs
file that sets up enough structure to enable you to do what you want:
Hi Eric,
my preferences are:
- source for code blocks. I think srcname looks ugly (although not as
ugly as tblname).
- call
- data and results for, well, data and results. With the same semantics
as Torsten Wagner suggested, i.e. a source block cannot change the
contents of a data block.
Hi Stephen,
AFAIK, there can only be one agenda view (an expert correct me, if I'm
wrong). But you can multiple blocks in the agenda. Search for Office
block agenda in:
http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.html
Cheers,
Viktor
Stephen J. Barr wrote:
Excellent.
Hi,
the text ='t'= is not recognized as code. Other markup doesn't work
either. If the quotes are in the middle (e.g. =foo'bar=) it is properly
recognized.
I'm using org-mode 7.7 pulled today from git.
Cheers,
Viktor
Hi Bernt,
Bernt Hansen wrote:
Geert Kloosterman g.j.klooster...@gmail.com writes:
Hi all,
On Wed, Oct 19, 2011 at 1:17 AM, Viktor Rosenfeld
listuse...@googlemail.com wrote:
org-todo-yesterday and org-agenda-todo-yesterday log a note using
the
current
Hi Susan,
swapping on OS X is usually accompanied by the spinning beach ball (from
hell).
Have you tried upgrading Emacs? I use Aquamacs (http://aquamacs.org/),
there's also Cocoa Emacs (http://emacsformacosx.com/). Both are based on
Emacs 23.3.
Cheers,
Viktor
Susan Addy wrote:
Also - it
Hi,
I'm trying to copy the values of a column in one table to another table
in. If I understand the manual correctly, this should be possible with
remote references. But I can't get it to work. In the example below, if
I evaluate the table formula, column 2 of table bar is copied into
column 3.
Nick Dokos wrote:
The manual says:
$3 = remote(FOO, @@#$2) copy column 2 from table FOO into
column 3 of the current table
and that works.
Thank you, Nick. Wer lesen kann, ist klar im Vorteil. (Those who can read
are at a clear advantage -- a
Hi Jonathon,
I have this in my .emacs file, maybe it helps.
(setq org-refile-allow-creating-parent-nodes (quote confirm))
Cheers,
Viktor
Jonathon Anderson wrote:
org-version 7.7
If I `C-c w` and attempt to refile a tree to the root of a file, the
minibuffer displays invalid target
Jonathon Anderson wrote:
On Mon, Nov 28, 2011 at 8:44 PM, Viktor Rosenfeld
listuse...@googlemail.com wrote:
I have this in my .emacs file, maybe it helps.
(setq org-refile-allow-creating-parent-nodes (quote confirm))
Yeah, I have that too. Or, similar.
Sorry, don't know how I missed
I use Bernt's approach with a few modifications. Basically I don't use
subprojects. I think Bernt's handling of subprojects is broken, because
a NEXT keyword burried in a subproject keeps the entire project off the
stuck projects lists. (Please correct me if I'm wrong.)
My solution is to move a
the project on a someday list.
Another solution would be to implement a stale projects list, i.e. a
list of projects that have defined next actions, but haven't seen any
work in the last X days.
Cheers,
Viktor
PS: Your org-mode site is generally the bomb!
Bernt Hansen wrote:
Viktor Rosenfeld
Hi,
I honestly liked the old one better. Some of my concrete criticism are:
- The old screenshot conveyed what org-mode was all about. Outlining
and project planning. The new screenshots take a lot longer to load
and even if you click on them, their content is not always accessible.
- I
Hi Bastien,
Bastien wrote:
- The old screenshot conveyed what org-mode was all about. Outlining
and project planning. The new screenshots take a lot longer to load
and even if you click on them, their content is not always
accessible.
I agree. Feel free to contribute to Worg
Hi,
the Worg page on LaTeX publishing covers this under Block-level Markup
and Inline Markup:
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-2
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-3
Haven't tried it myself so far (but planning to do so).
Hi,
Bastien wrote:
Viktor Rosenfeld listuse...@googlemail.com writes:
Can you make an alternate .css with non-fixed top bar and a better font?
Maybe on the weekend, but I can't promise anything.
Thanks in advance for this!
What's the git URL of the homepage repository?
Thanks
Hi,
you could enter the start using an inactive timestamp (optionally as a
property value). Then the entry would not show up on the agenda. The
Advanced searching tutorial on Worg explains how you can search for
inactive timestamps or property values:
Hi,
Thank you! That is interesting. Is my understanding correct, that you
meant something like the following.
* TODO Task, that can be completed tomorrow or later
START: [2011-12-19 Mon]
Either like this (which can be queried using TIMESTAMP_IA=2011-12-19
Mon or using a property
Karl Maihofer wrote:
Hi Viktor,
Viktor Rosenfeld listuser36 at googlemail.com writes:
I don't understand why it would show today. The date is in the future
(and it's not a deadline) and the timestamp is inactive. It should not
show up at all, unless the variable
org-agenda-include
Awesome, thanks!
Cheers,
Viktor
Bastien wrote:
Hi Vicktor,
Viktor Rosenfeld listuse...@googlemail.com writes:
is it possible to quickly limit what the agenda is showing to one
category?
Yes -- you can now use `' to filter the agenda through the category
from the current line
Hi,
I would like to include an entry of my org file in the exported Latex
file, but I would like the entry to be skipped in the table of contents.
In other words, I would like to reproduce the behavior of Latex commands
like \section* and so on. Is this at all possible?
I tried EXPORT_OPTIONS:
Hi Eric,
Eric S Fraga wrote:
Viktor Rosenfeld rosen...@informatik.hu-berlin.de writes:
Hi,
I would like to include an entry of my org file in the exported Latex
file, but I would like the entry to be skipped in the table of contents.
In other words, I would like to reproduce
Hi everybody,
I recently discovered inline tasks and use them to keep todos that are
related to a text I write close to the text. I'm not a big fan of their
visibility behavior, but I think I can manage.
I would very much like to clock work on inline tasks. However, when
opening a tasks with
Hi Bastien,
Bastien wrote:
Unfolding an inline task now keeps the drawers folded.
Thanks for the quick patch, but there's a small problem. The drawer is
collapsed if the inline task is opened, but not if the parent task is
opened.
Example:
* Parent Task
*** Inline Task
Hi Bastien,
Bastien wrote:
Fixed, thanks.
I first didn't take care of this because it seemed logical to
show all the content of an inline task here: the purpose of the
inline task is to stay out of the hierarchical structure, such
a task is *not* a subtree... so the real content of
Hi,
I have another question regarding inline tasks. When I start the clock
on an inline task the clocking information of the parent task is
included in the mode line. Is this the intended behavior?
In the example below there are three clock lines for a total of 1 hour
and 45 minutes. If I start
Hi,
I'm having trouble passing format strings (-F) to ledger using
org-babel. When I pass -F to :cmdline, I get the following error:
Not enough arguments for format string.
This appears to be a problem with the %-markup in the format string.
Posted below is a sample org file containing
Hi Eric,
I applied your patch locally and can confirm that it works.
Thank you,
Viktor
Eric S Fraga wrote:
Viktor Rosenfeld listuse...@googlemail.com writes:
Hi,
I'm having trouble passing format strings (-F) to ledger using
org-babel. When I pass -F to :cmdline, I get
Hi Piotr,
Piotr Isajew wrote:
- daily agenda having grid mode on, and displaying entries from
all categories
- weekly agenda having grid mode off and filtering out entries
from one specific category
With regard to the time grid you might want to check out the variable
Hi,
I've hacked the ox-koma-letter exporter to make it more configurable.
See the Changelog of the attached patch, hopefully I've followed the
Changelog guidelines propertly.
Also, I could not find an ox-koma-letter tutorial on Worg. I would be
willing to create such a tutorial, maybe next
Hi,
I have the following tags defined in my initialization code:
#+BEGIN_SRC emacs-lisp
(setq org-tag-alist '((:startgroup . nil)
(@home . ?h)
(@comp . ?c)
(@otg . ?o)
(@fon . ?f)
Hi Alan,
Alan Schmitt wrote:
Also, I could not find an ox-koma-letter tutorial on Worg. I would be
willing to create such a tutorial, maybe next weekend. Can anybody edit
the contents on Worg or do I need special priviledges?
You need to ask for write access.
Will do.
I started
Hi Alan,
Alan Schmitt wrote:
A couple notes about the patch:
- Could you create it using git format-patch? This way we'll have
more metadata in the commit.
I actually did that first and liked it more because then the patch was
split into more logical blocks (nine patches in total). However,
Hi Rasmus,
Rasmus wrote:
* Setting of KOMA options
The presence of the sender's phone and email, the letter's place and
subject, as well as foldmarks and the backaddress are
configurable. Consider:
#+OPTIONS: subject:titled place:nil phone:t email:t foldmarks:nil
backaddress:nil
Hi Bastian,
Bastien wrote:
Hi Viktor,
Viktor Rosenfeld listuse...@gmail.com writes:
If I hit the =/= key in the agenda to filter the agenda by tag, the
hotkeys defined in the list above are repeated multiple times.
Can you test this patch against latest maint or master branch
happens on your end?
Cheers,
Viktor
Alan
From 02727b4259b2530d7e878aeaed6b2d235d271f2a Mon Sep 17 00:00:00 2001
From: Viktor Rosenfeld hesk@cartman
Date: Sun, 21 Apr 2013 13:40:09 +0200
Subject: [PATCH 1/4] ox-koma-letter: Use same hotkeys as LaTeX export
* ox-koma-letter.el (koma-letter
Hi Rasmus,
Rasmus wrote:
In a similar spirit to subject is firsthead. First head is displayed
by default in scrlttr2 as far as I recall, which is annoying.
Is firsthead something that you change on a letter-by-letter basis? Or
do you configure it once for your letters and never change
Hi Alan,
Alan Schmitt wrote:
I'm still thinking that the default signature should be nil (so that the
option can be picked up from the LCO), but it's a minor nitpick.
Rasmus also suggested setting the default opening and closing to nil
because we should not assume that everybody speaks
Hi Alan,
Alan Schmitt wrote:
I've applied the patch. I propose a further tiny improvement:
,
| --- a/contrib/lisp/ox-koma-letter.el
| +++ b/contrib/lisp/ox-koma-letter.el
| @@ -273,7 +273,7 @@ holding export options.
|(when email (format \\setkomavar{fromemail}{%s}\n email))
|
Hi Johan,
this is fixed in master. The relevant commit is here:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=0fff0ba6da30e4ced73f84c8305d80c955bae132
Cheers,
Viktor
Johan Ekh wrote:
Hi all,
I've installed version 8 of org-mode and now I get the message not in an
item when I try to
Hi Bastien,
with this patch, everything works as expected.
Thanks!
Cheers,
Viktor
Bastien wrote:
Hi Viktor,
thanks for the patient and detailed debugging.
I don't have time to test the attached patch myself, but given your
description it should be okay.
Can you test it and report?
Hi,
the attached patch makes `org-agenda-filter-by-tag-refine' pickup the
hotkeys defined for tags in `org-tag-persistent-alist'.
Cheers,
Viktor
From 25d8eb08ecab282fc85c95307cddada8b5032e21 Mon Sep 17 00:00:00 2001
From: Viktor Rosenfeld listuse...@gmail.com
Date: Wed, 24 Apr 2013 15:54:14
Hi Alan,
I've removed the defaults from OPENING and CLOSING. See the attached
patch.
Cheers,
Viktor
Alan Schmitt wrote:
Viktor Rosenfeld writes:
Rasmus also suggested setting the default opening and closing to nil
because we should not assume that everybody speaks English. Maybe, every
the attached patch.
Cheers,
Viktor
Rasmus wrote:
Viktor Rosenfeld listuse...@gmail.com writes:
Yeah, I guess it's true. Still, since foldmarks depends on which
envelopes you have at hand it might make sense to have it accept a
string. In lisp-terms a string is still t. On the other hand
Hi Rasmus,
Rasmus wrote:
Viktor,
In a similar spirit to subject is firsthead. First head is displayed
by default in scrlttr2 as far as I recall, which is annoying.
Is firsthead something that you change on a letter-by-letter basis? Or
do you configure it once for your letters
at
./org-tutorials/koma-letter-export.org
Cheers,
Viktor
Alan Schmitt wrote:
Hi,
Viktor Rosenfeld writes:
Hi,
I've hacked the ox-koma-letter exporter to make it more configurable.
See the Changelog of the attached patch, hopefully I've followed the
Changelog guidelines propertly
Hi,
Rick Frankel wrote:
On Fri, May 03, 2013 at 09:14:43AM +0200, Carsten Dominik wrote:
On 2.5.2013, at 19:25, Leo Alekseyev dnqu...@gmail.com wrote:
Nice! Short and sweet, and works great. It should go on orgmode.org
somewhere in the cool hacks section.
Make a
Hi Alan,
Alan Schmitt wrote:
Hi Victor,
Viktor Rosenfeld writes:
Hi Rasmus and Alan,
I've changed the code so the value for foldmarks is passed through to
KOMA-Script. It's a bit ugly insofar as one has to specify
foldmarks:true to use the default values instead of other options
Hi,
commit 16f12e0 changed how the EMAIL option is configured in a derived
exporter that also uses this keyword.
In `contrib/ox-koma-letter.el', the koma-letter exporter configures the default
of the EMAIL option to the variable `org-koma-letter-email'. However, since
commit 16f12e0, if the
Hi Alan,
I just wanted to let you know that the tutorial is now online. I haven't
linked to it from the org-tutorials page yet, in case you want to take a
look. You can find it at
http://orgmode.org/worg/org-tutorials/koma-letter-export.html
Cheers,
Viktor
Alan Schmitt wrote:
Viktor Rosenfeld
Hi,
the attached patch fixes the problem. I wasn't sure if the logic simply
reverts the changes in commit 16f12e0 but it passes the test suite.
Cheers,
Viktor
Viktor Rosenfeld wrote:
Hi,
commit 16f12e0 changed how the EMAIL option is configured in a derived
exporter that also uses
Hi Nicolas,
Nicolas Goaziou wrote:
commit 16f12e0 changed how the EMAIL option is configured in a derived
exporter that also uses this keyword.
I fixed it in maint. Thank you for reporting it.
Thank you. Everything works as expected now.
Cheers,
Viktor
Regards,
--
Nicolas
Hi Suvayu,
Suvayu Ali wrote:
The convention is to put all documentation about the new exporters under
Worg.git/exporters. Take a look here:
http://orgmode.org/worg/exporters/
Thanks. I've also added an entry to the index file.
Cheers,
Viktor
Hope this helps,
--
Suvayu
Open
Hi Tom,
Thomas S. Dye wrote:
One small nit to pick, according to my dictionary meta data -
metadata.
Thanks, I've changed this.
Cheers,
Viktor
All the best,
Tom
Hi Rasmus,
Rasmus wrote:
Optionally download an up-to-date KOMA letter exporter
Is this something we want to encourage people to do?
We probably shouldn't. The problem is that the tutorial depends on
a version that has not yet been released. Once Org-mode 8.1 arrives the
best thing to do
Hi,
Alan Schmitt wrote:
Rasmus writes:
I found a bug in that the subject variable should be a list cf. the
KOMA manual. This patch fixes this.
It's pretty complex for something so simple, and I might be inclined
to admit to the put it in a LCO-file approach might be better.
I'd
Hi,
Rasmus wrote:
This is probably the most fun change. It adds special tags PS, ENCL,
CC, AFTER_CLOSING as in my last patch set, but it uses heading this
time. E.g. ENCLs are under the heading * ENCL :ENCL:. This was
suggested by Nicolas, and it's nicer. The ideas comes from
Hi,
Rasmus wrote:
Alan Schmitt alan.schm...@polytechnique.org writes:
OK, sounds good, I've applied it.
Actually, this patch does break LCO files. Now, if you don't set AUTHOR
or EMAIL in the letter the default options from the LaTeX exporter
always overwrite the settings defined in LCO
Hi,
Rasmus wrote:
This one just updates the credit: most importantly with Viktor.
Cool, thanks!
- Is it me or is there no option to have git send-email just fix a
the subject and heads and let the email program do the rest?! The
manual and various blog post did not reveal how on
Hi,
Haider Rizvi wrote:
Max Mikhanosha m...@openchat.com writes:
Hi All,
I've been writing some documentation in OrgMode with screenshots, and
as with any screenshot taking, it takes a while to get one just right.
A few tiny helper utilities, quickly snowballed into this :-) It
Forgot to attach the patch in my last mail.
Sorry about the double posting.
Viktor Rosenfeld wrote:
Hi,
Haider Rizvi wrote:
Max Mikhanosha m...@openchat.com writes:
Hi All,
I've been writing some documentation in OrgMode with screenshots, and
as with any screenshot taking
Hi,
Rasmus wrote:
Hi,
Now that 8.0 has shipped let's talk bibliography support. This
follows directly upon the discussion around March[1].
I did not follow the discussion in March and only skimmed through the
recent discussion in May [2]. But I was wondering if bibliography
support in
Hi,
I recently wrote a tutorial for the ox-koma-letter exporter [1] which
includes a link to an Org file [2] file and a PDF file [3] as examples.
The files are checked into the Worg repository, but they are not
available online. Is there something I have to do to enable this? At
first I thought
Hi,
Rasmus wrote:
Viktor Rosenfeld listuse...@gmail.com writes:
Actually, this patch does break LCO files. Now, if you don't set
AUTHOR or EMAIL in the letter the default options from the LaTeX
exporter always overwrite the settings defined in LCO files.
This one is tough. . .
One
Hi,
Rasmus wrote:
- It doesn't work because `org-koma-letter-special-content' is set to
nil at the beginning of `org-koma-letter-template'. Why is that? If I
comment it out everything works.
Hmm, it should be populated by the headline function each time. . .
That is at least the
Hi Rasmus,
Rasmus wrote:
Viktor Rosenfeld listuse...@gmail.com writes:
Or 5, keep the change from SENDER to AUTHOR but revert the default
values to `org-koma-letter-*' variables. (Right now the AUTHOR and EMAIL
lines could be removed because they duplicate the derived latex
backend
Hi,
Jay Kerns wrote:
Hello Viktor,
On Tue, May 21, 2013 at 2:13 PM, Viktor Rosenfeld listuse...@gmail.com
wrote:
Hi,
I recently wrote a tutorial for the ox-koma-letter exporter [1] which
includes a link to an Org file [2] file and a PDF file [3] as examples.
The files are checked
Hi,
Rasmus wrote:
Viktor Rosenfeld listuse...@gmail.com writes:
Ah, you mean the textsc? Perhaps it is a bit eccentric. But you're
bringing up a good point. It should recognize [p]+s and perhaps even
order them. . .
If there is no PS prefix set, users could simply write these out
Hi Rasmus,
Viktor Rosenfeld wrote:
Hi Rasmus,
Rasmus wrote:
Viktor Rosenfeld listuse...@gmail.com writes:
Or 5, keep the change from SENDER to AUTHOR but revert the default
values to `org-koma-letter-*' variables. (Right now the AUTHOR and EMAIL
lines could be removed because
Hi everybody,
Viktor Rosenfeld wrote:
I recently wrote a tutorial for the ox-koma-letter exporter [1] which
includes a link to an Org file [2] file and a PDF file [3] as examples.
The files are checked into the Worg repository, but they are not
available online. Is there something I
Hi Bastien,
Bastien wrote:
Hi Viktor,
Viktor Rosenfeld listuse...@gmail.com writes:
I believe I can give a partial answer: it looks like Worg isn't
publishing right now, which suggests that there was a recent commit
which broke things. The search for the problem begins. Once
Hi Bastien,
Bastien wrote:
Hi Viktor,
Viktor Rosenfeld listuse...@gmail.com writes:
However, the old version of the tutorial still shows at the old address.
I moved the file in the worg git repository from org-tutorials/ to
exporters/ but now there are two separate HTML copies. Do I
Hi Bastien,
Bastien wrote:
Hi Viktor,
Viktor Rosenfeld listuse...@gmail.com writes:
The files are:
- http://orgmode.org/worg/org-tutorials/koma-letter-export.html
- http://orgmode.org/worg/org-tutorials/koma-letter-example.html
Sorry for the inconvenience.
Deleted, thanks
a need
to grep LCO files.
Best regards
Robert
On 05/23/2013 12:06 AM, Viktor Rosenfeld wrote:
Hi Rasmus,
Viktor Rosenfeld wrote:
Hi Rasmus,
Rasmus wrote:
Viktor Rosenfeld listuse...@gmail.com writes:
Or 5, keep the change from SENDER to AUTHOR but revert the default
Hi Rasmus,
Rasmus wrote:
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
Viktor Rosenfeld writes:
Hi Robert,
Robert Klein wrote:
Hi,
FWIW, from
and associate it with the current default
list).
–Rasmus
--
This is the kind of tedious nonsense up with which I will not put
From bbaf9a6ddd75368b2143e6b8fb50be64bd66b50d Mon Sep 17 00:00:00 2001
From: Viktor Rosenfeld listuse...@gmail.com
Date: Thu, 23 May 2013 00:00:38 +0200
Subject
Hi Rasmus,
Rasmus wrote:
Rasmus ras...@gmx.us writes:
4. Sets defcustom org-koma-letter-signature nil since that
corresponds to default scrlttr2 behavior anyway (p. 183 in the
manual).
Re 4.: I'd like to do something similar to
org-koma-letter-subject-format. But I'm
Hi Robert,
Robert Klein wrote:
Hello,
On 05/25/2013 03:57 PM, Rasmus wrote:
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
Viktor Rosenfeld writes:
Hi Robert,
Robert Klein wrote:
Hi,
FWIW, from a users view it would be nice if:
- Use Author/Email
Hi Xavier,
Xavier Garrido wrote:
Hi koma-letterers,
Patches:
1. summarizes all changes in author. It uses my solution as mentioned
above.
2. full support for after closing keywords. See commit message
3. signature to nil
4. change handling of subject and allow for setting subject
Hello,
David Arroyo Menéndez wrote:
Hello,
I would like propose org-effectiveness to contrib. Org effectiveness is
a mode to measure the personal effectiveness using org todos.
+1
It should use `org-time-clocksum-use-effort-durations'. I definitely
like when my weekly clock report tells
Hi Alan,
Alan Schmitt wrote:
Hello,
I just had to write a new letter with a fresh LCO file, and I would like
to propose to change the priority of options. The current priority is:
local options emacs variables lco file.
Unfortunately emacs variables have a default value, which means
Hi Vikas,
Vikas Rawal wrote:
I am trying to use ox-koma-letter for my correspondence. I have a
functioning test file that produces a nice pdf. But I would like to
set it up so as to have one letter per headline, and do subtree export
to produce the pdf.
I am attaching the test file for
1 - 100 of 157 matches
Mail list logo