Bastien writes:
No, (require 'org-loaddefs) is never needed IMHO.
It is if you are using Org from Git and you only want the autoload
definitions pulled in on startup and not the whole of Org plus most of
its dependencies. This is what a
(require 'org-install)
did before the change to
Rafael Laboissiere raf...@laboissiere.net writes:
You might be interested in applying the patch attached below, which fixes
the comments in the *Remember* buffer, allowing them to get correctly
fontified.
Applied, thanks!
--
Bastien
Hello,
justus-b...@piater.name writes:
My current solution (see the patch) involves some minor refactoring at
the price of an extra (if ds ...) that I don't see a way to get rid of,
but I find the result quite readable.
It looks good. I would have integrated the (if ds ...) within the cond
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
It is if you are using Org from Git and you only want the autoload
definitions pulled in on startup and not the whole of Org plus most of
its dependencies. This is what a
(require 'org-install)
did before the change to org-loaddefs.el. You
Hello,
with an up to date org, I cannot get the attached minimal example to
export using the new exporter. I have try exporting to latex-pdf, in
case that matters. The (line-length truncated) error trace is:
--8---cut here---start-8---
Debugger entered--Lisp
Hi Eric,
You have:
#+include: uml.org
I think it should be:
#+include: uml.org
I have haven't tried it though.
Myles
Eric S Fraga writes:
Hello,
with an up to date org, I cannot get the attached minimal example to
export using the new exporter. I have try exporting to latex-pdf,
Hello,
this is my first post on the mailing list and i am not quite sure if i
do everything right. If i screw something up, please let me know, so i
can fix it and do it right next time.
To the problem I'm facing:
My setup: I have a single org file with appointments as sub trees.
Each
Nicolas Goaziou n.goaz...@gmail.com wrote on Sun, 28 Oct 2012 11:20:15
+0100:
I would have integrated the (if ds ...) within the cond (i.e (cond
((not ds) nil) ...))
Oh yes! Please do :-)
Justus
Hi Alexander,
Alexander Baier lexi.ba...@gmail.com writes:
(setq org-agenda-custom-commands
'((d Test Tag Filter
((agenda
((org-agenda-files '(~/org/WeeklyFilterTest.org))
(org-agenda-filter -EXCL)))
You need to locally bind
On 10/28/2012 12:58 PM, Alexander Baier wrote:
To explain what i want to achieve regarding this example: I want a
weekly agenda view only displaying Event1, Event2 and Event4 but not
Event3 as it should be excluded by its tag.
Any help is appreciated.
FWIW, my agenda is constructed like this:
Simon Thum simon.t...@gmx.de writes:
On 10/22/2012 10:38 PM, Eric Schulte wrote:
Simon Thumsimon.t...@gmx.de writes:
--8---cut here---start-8---
foo bar
--8---cut here---end---8---
all of the spaces and newlines
2012/10/28 Bastien b...@altern.org:
Hi Alexander,
Alexander Baier lexi.ba...@gmail.com writes:
(setq org-agenda-custom-commands
'((d Test Tag Filter
((agenda
((org-agenda-files '(~/org/WeeklyFilterTest.org))
(org-agenda-filter -EXCL)))
You need
Hello,
Myles English mylesengl...@gmail.com writes:
Given the situation below, I would expect that the block named xxx
would never be evaluated:
#- file b.org ---
#+TITLE: b.org
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
* A
On 10/28/2012 04:19 PM, Eric Schulte wrote:
Yes, the content of the edit boxes does come from the exported html.
For each portion of the Org-mode document (as delimited by
org-elements), both the raw Org-mode text and the HTML are exported
side-by-side, then the raw Org-mode text is hidden and
2012/10/28 Simon Thum simon.t...@gmx.de:
On 10/28/2012 12:58 PM, Alexander Baier wrote:
To explain what i want to achieve regarding this example: I want a
weekly agenda view only displaying Event1, Event2 and Event4 but not
Event3 as it should be excluded by its tag.
Any help is
Nicolas Goaziou n.goaz...@gmail.com writes:
I tend to think that :raw-value would be a good option. Timestamps
properties could be enriched. Besides common properties
(:begin, :end, :post-blank) timestamps objects may accept :
- :type
- :year-start
- :year-end
- :month-start
-
This commit broke editing any source section with blank lines.
Patch included.
--
Le
org-src.el.diff
Description: Binary data
Bastien writes:
You mean in case users install Org from a tar/zip archive that does
not contain org-loaddefs.el?
For now the tar/zip archives does not contain org-loaddefs.el but it
will starting from Org 7.9.3.
(require 'org-loaddefs) is wrong in case users who cloned Org from Git
forget
* Bastien b...@altern.org [2012-10-28 11:10]:
Rafael Laboissiere raf...@laboissiere.net writes:
You might be interested in applying the patch attached below, which fixes
the comments in the *Remember* buffer, allowing them to get correctly
fontified.
Applied, thanks!
Thanks.
I just
On Sat, Oct 27, 2012 at 5:57 PM, Eric Schulte schulte.e...@gmail.com wrote:
John Hendy jw.he...@gmail.com writes:
For papers and beamer presentations, I sometimes hide more universal
babel blocks inside a sort of setup headline. I thought I'd done this
before, but perhaps not... The idea
Hi, how does one tangle a single code block to multiple files?
I thought the following might work, but unfortunately it does not.
Set the frame size.
#+HEADERS: :tangle user-host-a.el user-host-b.el
#+BEGIN_SRC emacs-lisp
(setq initial-frame-alist '((width . 80) (height . 38)))
#+END_SRC
To
Just kidding... just checked *Messages* buffer, and all the headlines
I converted to COMMENT headlines are *not* executing the enclosed
babel blocks.
Is there a setting for this you have and I don't?
John
On Sun, Oct 28, 2012 at 12:23 PM, John Hendy jw.he...@gmail.com wrote:
On Sat, Oct 27,
Aloha Alan,
This can be achieved with noweb references.
Something like this:
#+name: user-host-a
#+HEADERS: :tangle user-host-a.el :noweb tangle
#+BEGIN_SRC emacs-lisp
initial-frame
#+END_SRC
#+name: user-host-b
#+HEADERS: :tangle user-host-b.el :noweb tangle
#+BEGIN_SRC emacs-lisp
Alan Lue alan@gmail.com writes:
Hi, how does one tangle a single code block to multiple files?
I thought the following might work, but unfortunately it does not.
Set the frame size.
#+HEADERS: :tangle user-host-a.el user-host-b.el
#+BEGIN_SRC emacs-lisp
(setq initial-frame-alist
Aloha Nicolas,
An example I gave on the ML a few days ago doesn't really work right.
#+name: fundamental-model
#+header: :exports results
#+header: :file fundamental-model.pdf
#+BEGIN_SRC dot
graph G
{
graph [margin=0.01];
d [label = Dated event, shape =box];
John Hendy jw.he...@gmail.com writes:
Just kidding... just checked *Messages* buffer, and all the headlines
I converted to COMMENT headlines are *not* executing the enclosed
babel blocks.
Is there a setting for this you have and I don't?
Not that I know of.
Are you using the new or the
Thanks Eric, I didn't know that you could pass lisp code as header
arguments. It looks like it'll be best to conditionally tangle.
:tangle (if (string-match myhost system-name) yes no)
Eric Schulte schulte.e...@gmail.com writes:
Alan Lue alan@gmail.com writes:
Hi, how does one tangle a
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
An example I gave on the ML a few days ago doesn't really work right.
#+name: fundamental-model
#+header: :exports results
#+header: :file fundamental-model.pdf
#+BEGIN_SRC dot
graph G
{
graph [margin=0.01];
d
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
An example I gave on the ML a few days ago doesn't really work right.
#+name: fundamental-model
#+header: :exports results
#+header: :file fundamental-model.pdf
#+BEGIN_SRC dot
graph G
When I provide a format string to the #+DATE: option, the old LaTeX exporter
correctly uses it to format the current date; the new exporter just uses the
format string for the date.
The new HTML exporter does not have this problem.
30 matches
Mail list logo
