I'm trying to create a custom agenda setup for my org-mode and I
wonder how I can sort the agenda-items by date (Scheduled or deadline):
newest first.I only found time-up / time-down in the parameters, but that does not seem to do what I need.Another
important point would be how to handle items
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha Jambu,
>
> Thanks for looking into this.
>
> Jambunathan K writes:
>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>
>>> Aloha all,
>>>
>>> Section 12.8.11.4 of the info version of the Org mode manual is
>>> truncated in the middle of an emacs-lisp co
Hi List,
I copied this from Bernt Hansens set-up:
,---
| org-insert-heading-hook is a variable defined in `org.el'.
| Its value is (bh/insert-heading-inactive-timestamp)
| Original value was nil
`---
Aloha Jambu,
Jambunathan K writes:
>
> I am able to scroll/move up/down the info node without any issues.
>
> In the tiff file that you have attached, the section heading
> corresponding to 12.8.11.4 is underlined with dots. For me, there is no
> such dotted underline in the node.
>
> Have you
Aloha Achim,
Achim Gratz writes:
> Thomas S. Dye tsdye.com> writes:
>> >> Section 12.8.11.4 of the info version of the Org mode manual is
>> >> truncated in the middle of an emacs-lisp code block.
>>
>> I see the full file in pdf and html.
>
> I get the complete section shown in Emacs and stand
Hello,
I think there's a bug when exporting files to ODT using environments
(center, quote etc.). Sample file:
* Testing
#+BEGIN_CENTER
First line.
Second line.
#+END_CENTER
When exporting that, only "First line" will have the correct style
OrgCenter. "Second line" (and all subsequent ones) w
It works!
Thanks Eric.
The backquote plus ',' did the job. I now understand why my previous
attempts didn't work and I can imagine what would be necessary to implement
the feature I requested (not worth it).
--
Darlan
At Tue, 29 Jan 2013 13:26:05 +0800,
Eric Abrahamsen wrote:
>
> Darlan Cavalc
Hi List,
when I export an Org file with Source blocks to LaTeX (:exports code),
the blocks are converted into environments of package 'listings':
,--
| \lstset{language=...}
| \begin{lstlisting}
| (def ... )
| \end{lstlisting}
`--
but:
1. the package i
If I load a python source file using python-mode.el, and then subsequently
look at a .org file using org-mode.el, I get an error:
Lisp error: (wrong-type-argument stringp nil)
and then I cannot see my .org file (nothing is displayed in the buffer).
Specifically the steps to reproduce are:
1) ru
Aloha Thorsten,
Thorsten Jolitz writes:
> Hi List,
>
> when I export an Org file with Source blocks to LaTeX (:exports code),
> the blocks are converted into environments of package 'listings':
>
What is the value of the variable org-export-latex-listings? If it is
'listings or 'minted, then
Apologies, this seems to have been fixed in the latest development sources
for python-mode.el.
Please disregard.
Thanks,
Greg
On Tue, Jan 29, 2013 at 3:12 PM, Greg Novak wrote:
> If I load a python source file using python-mode.el, and then subsequently
> look at a .org file using org-mode.e
t...@tsdye.com (Thomas S. Dye) writes:
Hi Tom,
> What is the value of the variable org-export-latex-listings?
,---
| org-export-latex-listings's value is t
`---
> If it is 'listings or 'minted, then there is quite a bit of
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I have the following two macros:
>
> #+MACRO: markup @@info:@$1{@@$2@@info:}@@
> #+MACRO: kbd {{{markup(kbd,$1)}}}
>
> When I export to texinfo using the new exporter, the following macro
> call triggers an error (byte-code: Wrong type argument: con
Hi,
The date/time prompt, as described at [1], helps me a lot to quickly go
over items and (re-)schedule or put a deadline to them.
It has bitten me a couple of times though where I typed
'3-2' where my intention was to put it at the 'third of february' and
ended up with something at the 'second
Hi Thorsten,
Thorsten Jolitz writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
> Hi Tom,
>
>> What is the value of the variable org-export-latex-listings?
>
> ,---
> | org-export-latex-listings's value is t
> `---
>
>> If
Nicolas Goaziou writes:
>
> I didn't try it, but it probably comes from the syntax of macros, which
> is a bit brittle wrt commas.
>
> We ought to modify it. Perhaps something like:
>
> {{{name arg1 "arg2 with space" "arg3 \"with\" quote"}}}
So, with the modification, I'd write {{{kbd("C-,")}}
Thorsten Jolitz writes:
> I copied this from Bernt Hansens set-up:
>
> ,---
> | org-insert-heading-hook is a variable defined in `org.el'.
> | Its value is (bh/insert-heading-inactive-timestamp)
> | Original value was nil
> `
Hi Marcel,
Marcel van der Boom wrote:
> The date/time prompt, as described at [1], helps me a lot to quickly go
> over items and (re-)schedule or put a deadline to them.
> It has bitten me a couple of times though where I typed
> '3-2' where my intention was to put it at the 'third of february' a
On Tue 29-Jan-2013 21:00
"Sebastien Vauban" wrote:
> Marcel van der Boom wrote:
>> The date/time prompt, as described at [1], helps me a lot to quickly
>> go over items and (re-)schedule or put a deadline to them.
>> It has bitten me a couple of times though where I typed
>> '3-2' where my int
Hello,
Please find here an enriched log of the packages which are loaded for Org, and
the time it takes.
--8<---cut here---start->8---
[2013-01-29 21:20:18] (info) +-> Requiring `appt'...
[2013-01-29 21:20:18] (info) +-> Requiring `diary-lib'...
[2013-01-29 2
Marcel van der Boom wrote:
>
>
> On Tue 29-Jan-2013 21:00
> "Sebastien Vauban" wrote:
>
> > Marcel van der Boom wrote:
> >> The date/time prompt, as described at [1], helps me a lot to quickly
> >> go over items and (re-)schedule or put a deadline to them.
> >> It has bitten me a couple of t
"Sebastien Vauban" writes:
> Hello,
Hello Sebastien,
> I would like to have:
>
> - the minimal Org config loaded when opening any .org file; IOW, certainly not
> the agenda files!
>
> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>
> - the current clocked file whe
Hi everyone.
I'm using org-mode from ELPA.
1. Which require statements should and should not be in my init file?
2. Are there any easy tests I can do to make sure everything is working
properly? M-x org-version is giving me a good answer, just wondering
about anything else.
--
Thanks
Dav
Hello Daimrod,
Daimrod wrote:
> "Sebastien Vauban" writes:
>> I would like to have:
>>
>> - the minimal Org config loaded when opening any .org file; IOW, certainly
>> not
>> the agenda files!
>>
>> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>>
>> - the current
Sebastien Vauban wrote:
> In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
> 21:20:46. They correspond to the executiong of just *one line*:
>
> #+begin_src emacs-lisp
> (org-agenda-to-appt)
> #+end_src
>
> This may have something to do with my big amount of Org fi
"Sebastien Vauban" writes:
> Hello Daimrod,
>
> Daimrod wrote:
>> "Sebastien Vauban" writes:
>>> I would like to have:
>>>
>>> - the minimal Org config loaded when opening any .org file; IOW, certainly
>>> not
>>> the agenda files!
>>>
>>> - all files in `org-agenda-files' when calling any ag
Thomas S. Dye writes:
> (/Users/dk/.emacs.d/src/org-mode/doc/./org.texi
> (/Users/dk/.emacs.d/src/org-mode/doc/texinfo.tex
> Loading texinfo [version 2012-01-03.18]: pdf, fonts, page headings, tables,
> conditionals, indexing, sectioning, toc, environments, defuns, macros,
> cross references, inser
Nick Dokos writes:
> (untested) I believe you can enter dates in "european dot" notation:
>
> 2013.2.3
I don't know any place in Europe using such a format, the one that is
used at least here is D[D].M[M].[YY[YY]] (but it also suffers from the
same sort of potential ambiguity and confusio
Hi Nick,
Thanks for looking into this as well!
Nick Dokos wrote:
> Sebastien Vauban wrote:
>> In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
>> 21:20:46. They correspond to the executiong of just *one line*:
>>
>> #+begin_src emacs-lisp
>> (org-agenda-to-appt)
>>
Daimrod,
Daimrod wrote:
> "Sebastien Vauban" writes:
>> Daimrod wrote:
>>> "Sebastien Vauban" writes:
I would like to have:
- the minimal Org config loaded when opening any .org file; IOW, certainly
not
the agenda files!
- all files in `org-agenda-files' whe
Achim Gratz wrote:
> Nick Dokos writes:
> > (untested) I believe you can enter dates in "european dot" notation:
> >
> >2013.2.3
>
> I don't know any place in Europe using such a format, the one that is
> used at least here is D[D].M[M].[YY[YY]] (but it also suffers from the
> same sort
Sebastien Vauban wrote:
> >> This may have something to do with my big amount of Org files in
> >> `org-agenda-files': 36 at this point. But is that so big??
> >
> > I don't think so.
>
> I'm sure it is, as I wrote (removed from the joined log) a "message" call
> before and after that line, and
Hi David,
David Rogers writes:
> 1. Which require statements should and should not be in my init
> file?
None.
You just need to initialize the package configuration with
(package-initialize)
before using any Org autoloaded function in your .emacs file.
> 2. Are there any easy tests I can
Hi Achim,
I found my way to the top of the 'make update' output. It looks like
makeinfo thinks all is well (assuming its complaints would be visible
here):
makeinfo --no-split org.texi -o org
makeinfo --html --number-sections --no-split -o org.html org.texi
Achim Gratz writes:
>> These are t
HI Sébastien,
"Sebastien Vauban"
writes:
> In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
> 21:20:46. They correspond to the executiong of just *one line*:
>
> #+begin_src emacs-lisp
> (org-agenda-to-appt)
> #+end_src
>
> This may have something to do with my big
Bit of an off-topic comment.
The website for org-mode (http://orgmode.org/) is fantastic. It's well
laid out, helpful, and beautiful to look at. Whoever's in charge of
maintaining it is doing a great job!
Thanks,
--
Aubrey
"There are two types of people in the world: those who
can extrapolat
I've sent some messages to this list about a bug that manifests in
org-mobile (although the cause is in orgmode itself, and is not
specific to org-mobile). One of those messages is a bug report, with
steps to reproduce that do not depend on having MobileOrg set up (so
anyone can look at it, not onl
37 matches
Mail list logo
