Hi Nick,
I tried moving org-capture.elc out of the way and reloading Org, but
with the same results. Starting emacs again didn't make a difference.
I'm still getting org-refile: Invalid function: with-demoted-errors
All the best,
Tom
Nick Dokos writes:
> Thomas S. Dye wrote:
>
>> Aloha all,
At Mon, 29 Oct 2012 17:07:23 +0100,
Sebastien Vauban wrote:
>
> Hello Erik and Bastien,
>
> […]
>
> I share your point...
>
> But do we all agree that your original example had to fail when
> LOG_INTO_DRAWER is not inherited?[1]
>
> Or do I miss some point?
>
> Seb
Hi Sebastien,
Yes, I had a
Thomas S. Dye wrote:
> Aloha all,
>
> With a recent make update from Git I'm getting this error when I try to
> Finish (with C-c C-c) some tried and true capture templates:
>
> org-capture-bookmark-last-stored-position: Invalid function:
> with-demoted-errors
>
> Here is a backtrace:
>
> Deb
Aloha all,
With a recent make update from Git I'm getting this error when I try to
Finish (with C-c C-c) some tried and true capture templates:
org-capture-bookmark-last-stored-position: Invalid function: with-demoted-errors
Here is a backtrace:
Debugger entered--Lisp error: (wrong-type-argumen
Christopher Schmidt wrote:
> Nick Dokos writes:
> > What missing variable definition? By the time the export is finished,
> > the let-bind is gone. There is no definition of TeX-master anywhere,
> > just as if you never had org loaded: why should auctex object to that?
> >
> > So I don't underst
Hello,
"Sebastien Vauban"
writes:
> Can we assume that `:noexport:' and `COMMENT' are complete synonyms, as of
> today
As of today, yes.
> and will stay so in the foreseen future?
I wouldn't bet. `:noexport' is /de facto/ limited to export. `COMMENT'
keyword doesn't have to. Someone may com
Michael Gauland wrote:
> Nicolas Goaziou gmail.com> writes:
>
> > I just tried with a minimal init and it worked. Could you send the
> > example you're trying to export?
>
> The file is below. With a minimal init, I get the error "Symbol's function
> definition is void: org-macro-initialize-te
Nick Dokos writes:
> What missing variable definition? By the time the export is finished,
> the let-bind is gone. There is no definition of TeX-master anywhere,
> just as if you never had org loaded: why should auctex object to that?
>
> So I don't understand why it would break: all the common sc
Nicolas Goaziou gmail.com> writes:
> I just tried with a minimal init and it worked. Could you send the
> example you're trying to export?
The file is below. With a minimal init, I get the error "Symbol's function
definition is void: org-macro-initialize-templates'. If I use my full .emacs
file,
Hi,
Running Fedora 17 and org-mode 7.9.2 I have just updated texlive from
the default repos to texlive-2012 and installed
texlive-collection-latexextra, but have problems to export org-files to
pdf. The error message received says:
,
| !pdfTeX error: pdflatex (file cm-super-t1.enc): cannot ope
Christopher Schmidt wrote:
> Nick Dokos writes:
> > In any case, if you can get rid of the let-bind (or the need to muck
> > with TeX-master at all within org), without introducing a regression,
> > we are all ears.
>
> I think adding (require 'tex nil t) before the let form is a nice fix.
>
Michael Gauland writes:
> Nicolas Goaziou gmail.com> writes:
>> On the other hand, you have a hard-coded macro to solve this problem:
>>
>> #+DATE: {{{time(%c)}}}
>>
>> It will work across every back-end (but you need the latest Org version,
>> since I recently to fixed a bug related to it).
Hi Nicolas and Eric,
Eric S Fraga wrote:
> It's a problem only because of the way I use the :noexport: and COMMENT
> tags to exclude parts of a document that are often incomplete or
> partially defined.
Can we assume that `:noexport:' and `COMMENT' are complete synonyms, as of
today, and will sta
Nicolas Goaziou gmail.com> writes:
> On the other hand, you have a hard-coded macro to solve this problem:
>
> #+DATE: {{{time(%c)}}}
>
> It will work across every back-end (but you need the latest Org version,
> since I recently to fixed a bug related to it).
Thanks--that will do nicely. Unf
Nick Dokos writes:
> In any case, if you can get rid of the let-bind (or the need to muck
> with TeX-master at all within org), without introducing a regression,
> we are all ears.
I think adding (require 'tex nil t) before the let form is a nice fix.
IMO the situation ATM is pretty bad. If AUC
Nicolas Goaziou writes:
> Hello,
>
> Eric S Fraga writes:
>
>> There is still a bug in that the exporter should fail more gracefully?
>
> Agreed. This syntax error should be more explicit now. Thanks.
Thanks!
>> The question of structural interpretation remains: should the file be
>> included
Hi Sébastien,
Sébastien Delafond writes:
> Hi fellows,
>
> just got the following bug report[0] from a Debian user:
>
> Typing C-c C-v t on the following file creates only bar.txt but not
> foo.txt as expected.
I just tried this with the git head and get the two files. Of course,
it doesn'
Hello,
Samuel Wales writes:
> Debugger entered--Lisp error: (void-function org-clocking-buffer)
> org-clocking-buffer()
> org-element-headline-parser(1375194 t)
> org-element-at-point()
> org-mark-element()
> org-mark-subtree()
>
> If it is related, then you have to load org-clock to m
This patch makes None being treated as hline again.
Best regards
Lennart Fricke
diff --git a/lisp/ob-python.el b/lisp/ob-python.el
index 71adf73..a1f834f 100644
--- a/lisp/ob-python.el
+++ b/lisp/ob-python.el
@@ -123,7 +123,11 @@ specifying a variable of the same value."
"Convert RESULTS into
Hello,
The following block exits with error:
orgtbl-format-line: Wrong type argument: sequencep, None
#+TBLNAME: many-cols
| a | b | c |
|---+---+---|
| d | e | f |
|---+---+---|
| g | h | i |
#+NAME: echo-table
#+BEGIN_SRC python :var tab=many-cols :hlines yes
return tab
#+END_SRC
I
I have been looking at trying to track training performance with
org-mode.
I currently just set a reoccurring schedule with note logging on
state change, but wondered if there was a way to log values within
this :LOGBOOK: logs?
It is not a lot of effort to simply type in ":abc: 5", etc in the not
Hello Erik and Bastien,
Erik Hetzner wrote:
> Bastien wrote:
>> 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
At Mon, 29 Oct 2012 06:41:39 +0100,
Bastien wrote:
>
> 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
Hello,
Ista Zahn writes:
> Here is what I did:
>
> 1. Update to latest git version
> 2. Start emacs with emacs -Q -l ~/test.el (test.el attached)
> 3. Create minimal org file, e.g.,
>
> #+title: test
>
> * Heading 1
>
> * Heading 2
>
> 4. Export with M-x org-export-dispatch t a
>
> What happened
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 posted to the Org-mode mailing list.
--
Hi,
I tried with both the old exporter (emacs -Q) and the new.
The old one exports correctly on my side, here's the relevant part:
#+BEGIN_LaTeX
This is Bar.
\subsection{Bar 1}
\label{sec-2-1}
This is Bar's first part.
\subsection{Bar 2}
\label{sec-2-2}
And here is the second
On 2012-10-27, Bastien wrote:
> I agree. Let's start by patching README_contribute with a new
> section containing short documentation for contributions.
Hi Bastien,
I unfortunately have very little time these days to take on this task
:\ Hopefully this will change in the not-too-distant future
Hello,
Eric S Fraga writes:
> There is still a bug in that the exporter should fail more gracefully?
Agreed. This syntax error should be more explicit now. Thanks.
> The question of structural interpretation remains: should the file be
> included if it is found within a not-to-be-exported head
Hello,
If you have such a Sh code block in any Org document, you'll see that the 4th
line will be highlighted as an Org comment from the "# != 2"...
#+begin_src sh
# swap FILE1 FILE2
swap ()
{
if [[ $# != 2 ]]; then
return 1
fi
tmpfile=/tmp/.swapper.$$.$RANDOM
mv -f $1 $tm
Hello,
Michael Gauland writes:
> 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.
I wasn't aware of that "feature". Though, I don't like it: it is fragile
for
Myles English writes:
> Hi Eric,
>
> You have:
>
> #+include: uml.org
>
> I think it should be:
>
> #+include: "uml.org"
Indeed it should be, or at least for the new exporter. Thanks for
pointing this out.
There is still a bug in that the exporter should fail more gracefully?
The question
Bastien writes:
> Sorry, maybe I was unclear, but I'm looking forward to reading
> a *recipe* to reproduce the bug.
Bastien,
I think what Achim is saying is that, for those of us that install org
from git, the system of autoloading is *fragile* because it depends on
non-predictable behaviour of
On 2012-10-08, Sébastien Delafond wrote:
> Since the update to org-mode 7.9.1-1, the LaTeX export does not work
> completely anymore with included files.
No idea at all on this one ? :)
Cheers,
--Seb
Hi fellows,
just got the following bug report[0] from a Debian user:
Typing C-c C-v t on the following file creates only bar.txt but not
foo.txt as expected. Does it matter whether BEGIN_SRC and END_SRC are
written in small letters or not?
The <..> lines are not part of foo.org
#+
Ho!
I was thinking that giving the more details will eliminated doubts and
misunderstanding.
So to be clear enough, there was two questions in my previous message:
1/ In E-LISP, how to parse a directory containing Org files and import them
with the "#+INCLUDE" function?
I used those two functio
The edit option comes only for the content of the headings. We can't edit
the headings and the subheadings of the headings.
So the source code has to be modified to make the org-mode document
editable as HTML where we can edit the Headings and subheadings.
The edit button appears only for the conte
Bastien writes:
> Sorry, maybe I was unclear, but I'm looking forward to reading
> a *recipe* to reproduce the bug.
Build an Emacs without Org or remove all autoload forms for Org from
loaddefs.el, then install a standalone Org and don't add any requires to
the startup files. Try to use any Org f
Sorry, maybe I was unclear, but I'm looking forward to reading
a *recipe* to reproduce the bug.
I will re-read your email when I have time to parse it in full
details.
Thanks,
--
Bastien
Hi Lennart,
Lennart Fricke writes:
> I don't think that it is necessary any more.
Good, thanks for the update!
Best,
PS: the emacs-devel team is great.
--
Bastien
Bastien writes:
> Can you point at an actual reproducible and simple bug with
> the current way Org defines autoloads?
After the introduction of org-loaddefs, the autoloads should be
extracted into two files and only the first is supposed to be loaded
before org is actually used and the second, or
Hi Bastien!
I don't think that it is necessary any more.
It's a bug in tmm and lacarte. The keymap sturcture changed in Emacs 24.
See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12744
I also posted on DrewAdams emacswiki site.
Best regards
Lennart Fricke
Achim Gratz writes:
> Bastien writes:
>> What is "autoload-rubric"?
>
> C-h f autoload-rubric
>
> autoload-rubric is a compiled Lisp function in `autoload.el'.
Thanks. The function is not autoloaded, so I had to
(require 'autoload) before being able to access it.
--
Bastien
Bastien writes:
> What is "autoload-rubric"?
C-h f autoload-rubric
autoload-rubric is a compiled Lisp function in `autoload.el'.
(autoload-rubric FILE &optional TYPE FEATURE)
Return a string giving the appropriate autoload rubric for FILE.
TYPE (default "autoloads") is a string stating the type
Hi Mark,
Mark Edgington writes:
> I hacked together a python script based on some already-existing code,
> which allows one to push an org file to a google-tasks list, or to
> pull the contents of a google-tasks list into an org file. Though the
> code isn't beautiful at the moment, it is funct
44 matches
Mail list logo
