Hi Achim,
let's start fresh.
Can you point at an actual reproducible and simple bug with
the current way Org defines autoloads?
Thanks,
--
Bastien
Hi Achim,
Bastien writes:
>> + (write-region (autoload-rubric "org-install.el" nil "org-install") nil
>> "org-install.el")
>> + (write-region (autoload-rubric "org-loaddefs.el" nil "org-loaddefs") nil
>> "org-install.el")
>
> I don't know what "autoload-rubric" is. Hint?
You didn't reply t
Le Wang writes:
> This commit broke editing any source section with blank lines.
Er.. yes, indeed. Thanks for the fix! I just applied it.
--
Bastien
Hi Erik and Sébastien,
Erik Hetzner writes:
> The function org-log-into-drawer called the function org-entry-get
> with the inherit argument before I got there. (Maybe it needs to be
> added to that list?)
I don't have time to look deeper in this issue. Can one of you have a
closer look at the
Hi Alexander,
Alexander Baier writes:
> Another question: Do you know if there is any documentation on the
> settings i can pass to the commands in org-agenda-custom-commands?
Not sure it answers your question correctly, but here is a good
tutorial about this configuration area:
http://orgmode
Hi Lennart,
Lennart Fricke writes:
> Hello everybody, I was trying to use org-mode from console and realized
> that there are no Org-Mode menus when I open the text menu with
> (tmm-menubar) or lacarte.
Bug confirmed.
> Do you have an idea why there are not there.
This is actually a bug in
Nicolas Goaziou writes:
> Done. I've also added :repeater-unit for good measure.
Great, thanks!
--
Bastien
Hi Rafael,
Rafael Laboissiere writes:
> I just noticed that my patch have a bad side effect, since the commented
> lines at the beginning of the *Remember* buffer are not filtered out before
> inclusion into the destination org file. The patch attached below fixes
> this. Also, the org-remembe
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.
Nicolas Goaziou 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
>>
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"];
>
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 writes:
> Alan Lue writes:
>
>> Hi, how does one tangle a single code block to multiple f
John Hendy 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 old exporter?
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"];
Alan Lue 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 '((width . 80)
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
<>
#+END_SRC
#+name: user-host-b
#+HEADERS: :tangle user-host-b.el :noweb tangle
#+BEGIN_SRC emacs-lisp
<>
#+END_SRC
#+name: i
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 wrote:
> On Sat, Oct 27, 2012 at 5:57 PM, Er
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 p
On Sat, Oct 27, 2012 at 5:57 PM, Eric Schulte wrote:
> John Hendy 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 would be like so:
>>
>> * Data setu
* Bastien [2012-10-28 11:10]:
Rafael Laboissiere 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 noticed that my patch have a bad side effe
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
This commit broke editing any source section with blank lines.
Patch included.
--
Le
org-src.el.diff
Description: Binary data
Nicolas Goaziou 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
> - :month-end
2012/10/28 Simon Thum :
> 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.
>
>
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 th
Hello,
"Myles English" 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 heading
2012/10/28 Bastien :
> Hi Alexander,
>
> Alexander Baier 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
Simon Thum writes:
> On 10/22/2012 10:38 PM, Eric Schulte wrote:
>> Simon Thum writes:
>> --8<---cut here---start->8---
>> foo bar
>>
>>
>>
>>
>>
>> --8<---cut here---end--->8---
>>
>> all of the spaces and newlines are inse
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:
Hi Alexander,
Alexander Baier 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 `org-agenda-tag-filter-preset'
Nicolas Goaziou 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
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 appointmen
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
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--Lis
Hi Achim,
Achim Gratz 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 can't rely
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
Rafael Laboissiere 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
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 org-load
38 matches
Mail list logo
