Hi Katepano,
katepano writes:
> By the way nobody responded to my message!!!
>
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
Please be patient -- I have been busier than expected lately and
I could not read/reply all emails. If nobody else replied to it,
it doesn't mean it'
[forgot to cc: the list]
Izzie wrote:
> Reading the manual, I found myself needing a single page version which
> I found after a quick search, I noticed that org mode manual is
> offered in several formats but not as much as emacs'[1]., which made
> me wonder if there is a org manual plain text
Reading the manual, I found myself needing a single page version which
I found after a quick search, I noticed that org mode manual is
offered in several formats but not as much as emacs'[1]., which made
me wonder if there is a org manual plain text version that can be
downloaded somewhere.
I also
Hullo,
2011/4/4 Sébastien Vauban :
> [snip]
>
> When discussing exporters and features, two things that come up to my mind as
> missing as a "general Org feature":
>
> - bibliography :: works for LaTeX[1], not for HTML export.
> - acronyms :: idem.
>
> Maybe those should be made available for gene
Tom gmail.com> writes:
>
> Bottom line: the problem does not occur in the English locale,
> because there all day abbreviations are 3 chars long, so the
> above described simple way of restoring the cursor position
> always works. But this is not true for all locales, so org
> shouldn't rely on t
* lisp/org-agenda.el: Remove obsolete code for adding todo list in front
of the agenda
Todo lists should be built with the TODO list or a block agenda instead.
This code was triggered for C-u R in block agendas which is used to
limit the clock report to the current tags filter applied to the
agen
Appended is a patch with a couple of small changes to org-taskjuggler.el,
addressing the following issues:
General:
* in org-taskjuggler-open-project, the duration is never calculated (default is
always used).
Specific to tj3:
* the reports need a "formats" attribute
* tj3 does not support t
Could one not have it go into a temporary file and then have an exit
hook attatched to a particular template that if a particular property
had been filled in that it would create a new file with that name and
either refile to or cut to and then paste from the kill ring?
Matthew
obviously would re
At Thu, 31 Mar 2011 00:06:52 +0200,
Michael Heerdegen wrote:
>
>
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be
At Fri, 1 Apr 2011 13:43:06 -0400,
Buck Brody wrote:
> Is there a way to use capture to create new files? Can I fill out
> the name of the file, and add a date stamp, from within the capture
> template?
Prompting in the templates happens after the template is placed in the
target buffer. So AFAI
On 4.4.2011, at 19:57, Nick Dokos wrote:
> Bernt Hansen wrote:
>
>> katepano writes:
>>
>>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
>>> does not work
>>
>> Something happened to it? This feature was not removed intentionally.
>> I don't use this feature so
Bernt Hansen writes:
> katepano writes:
>
>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
>> does not work
>
> Something happened to it? This feature was not removed intentionally.
Actually I stand corrected. Carsten added the "DOES NOT WORK" text to
the info manu
Bernt Hansen wrote:
> katepano writes:
>
> > what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
> > does not work
>
> Something happened to it? This feature was not removed intentionally.
> I don't use this feature so I can't verify if it works or not without
> more inf
katepano writes:
> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
> does not work
Something happened to it? This feature was not removed intentionally.
I don't use this feature so I can't verify if it works or not without
more information.
Please provide an example o
katepano wrote:
> what happen to the #+OPTIONS: \n:t ? we need it back please!!!
Why? what's the use case?
> why it
> does not work
>
> By the way nobody responded to my message!!!
>
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
>
> why? is it a stupid question or it
Vitalie Spinu writes:
> Hello everyone!
>
> Have a file like this:
>
> #+OPTIONS:H:3 num:nil toc:2 \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t
> LaTeX:t skip:t d:(HIDE) tags:not-in-toc
> #+BABEL: :exports both :session *R* :cache no
> #+TBLNAME: Chu
Matt Lundin wrote:
> Hi Jambunathan,
>
> Jambunathan K writes:
>
> > Matt Lundin writes:
> >
> >> I agree that the org-exporter currently does its job very well. The
> >> astounding utility of org-mode is ample proof of the value of releasing
> >> early; even if the exporter is not as elegant
Sébastien Vauban wrote:
> Hi Nick and al.,
>
> Nick Dokos wrote:
> >> This will at least help with the first difficulty -- and motivate all
> >> people working on the exporters to address the second one. The third one
> >> can be turned into a *chance*: that of having several people working in t
IIRC org-add-note works in a way that is unexpected. I think it makes
its actions happen after the command itself. I got bitten by that for
something else; maybe it is related here.
Samuel
--
The Kafka Pandemic:
http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forc
Hi Jambunathan,
Jambunathan K writes:
> Matt Lundin writes:
>
>> I agree that the org-exporter currently does its job very well. The
>> astounding utility of org-mode is ample proof of the value of releasing
>> early; even if the exporter is not as elegant as a modern compiler, it
>> works. :)
Hello everyone!
Have a file like this:
#+OPTIONS:H:3 num:nil toc:2 \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t
LaTeX:t skip:t d:(HIDE) tags:not-in-toc
#+BABEL: :exports both :session *R* :cache no
#+TBLNAME: Chuah07
| condition | Mean.offer |
|
Hi Brian,
On Mon, 4 Apr 2011 11:57:30 -0400
brian powell wrote:
> * http://www.emacswiki.org/emacs/WinnerMode gives:
>
I am a little confused, aren't windmove and winner mode different
packages? I use both, but I narrowed down the problem to just
winner-mode.
> "The problem with (windmove-def
* http://www.emacswiki.org/emacs/WinnerMode gives:
"The problem with (windmove-default-keybindings) is that they clash
with the more common use on modern systems of S-right etc for
selecting text. In Emacs this is turned on by CuaMode for example.
Therefore it might be better to go with the altern
Hi Nick and al.,
Nick Dokos wrote:
>> This will at least help with the first difficulty -- and motivate all
>> people working on the exporters to address the second one. The third one
>> can be turned into a *chance*: that of having several people working in the
>> same direction.
>
> Excellent pl
what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
does not work
By the way nobody responded to my message!!!
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
why? is it a stupid question or it can't be implemented?
Regards
katepano
Matt Lundin writes:
> Eric S Fraga writes:
>
>> Jambunathan K writes:
>>
>> [...]
>>
>>> I think one of the reasons Org is so popular it is that it is a
>>> common-man's swiss army knife and not a elitist samurai sword.
>>
>> And I think this is a very important analogy. Org does a good job fo
Eric S Fraga writes:
> Jambunathan K writes:
>
> [...]
>
>> I think one of the reasons Org is so popular it is that it is a
>> common-man's swiss army knife and not a elitist samurai sword.
>
> And I think this is a very important analogy. Org does a good job for
> many (very different) tasks.
> "Bernt" == Bernt Hansen writes:
Bernt> Hi Frederic,
Bernt> So does this mean it's fixed in origin/master but broken in
Bernt> release_7.5? Is your original task in the same file as the
Bernt> target of your capture?
Yes, it is.
Bernt> There were a few fixes to the co
28 matches
Mail list logo
