Hi Achim,
On Wed, Oct 10, 2012 at 06:05:59PM +0200, Achim Gratz wrote:
Achim Gratz writes:
What is not working is re-loading of org-export-latex. How it manages to
drop
the name and make nil out of this I don't know (yet).
Some files in Org provide more than one feature and at least
Suvayu Ali writes:
I have a couple of third party org libraries that are causing this
problem for me. I couldn't follow the discussion properly, could you
please elaborate how I might fix these libraries so that org-reload
works properly?
Whatever your problem is, it's clearly different from
Hi Achim,
On Thu, Oct 11, 2012 at 08:17:57PM +0200, Achim Gratz wrote:
Suvayu Ali writes:
Here are my messages:
Some error occured while reloading Org features
(org-occur-goto org-search-goto)
Please check *Messages*!
Org-mode version 7.9.2 (release_7.9.2-434-gc23dea @ ...)
Suvayu Ali writes:
I thought I skimmed through it, but I apparently missed them! Anyway
they do return t but it is obvious from the message below that
org-reload does not like that these libraries are not in the usual org
directories (they are not part of contrib).
They are not part of Org,
On Thu, Oct 11, 2012 at 09:06:42PM +0200, Achim Gratz wrote:
Suvayu Ali writes:
I thought I skimmed through it, but I apparently missed them! Anyway
they do return t but it is obvious from the message below that
org-reload does not like that these libraries are not in the usual org
Hello,
Achim Gratz strom...@nexgo.de writes:
Suvayu Ali writes:
I thought I skimmed through it, but I apparently missed them! Anyway
they do return t but it is obvious from the message below that
org-reload does not like that these libraries are not in the usual org
directories (they are
Nicolas Goaziou writes:
By the way shouldn't testing/ and testing/lisp/ directories be allowed
to contain features? At the moment reloading with feature `org-test'
present returns errors like:
It's a warning, not an error. It's there so that you aren't missing
when a file is not loaded from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/10/12 19:37, Achim Gratz wrote:
Rainer M Krug writes:
When reloading org after update, I get the following messages in the message
buffer, where
there is apparentkly an error - but I can't see any?
It's a bug in org-reload, please pull
Rainer M Krug r.m.krug at gmail.com writes:
unfortunately I still get the same message (below)
I don't see how this is possible unless one of the loaded
files returns '(nil)' instead of 't' when loaded. Could
you go to org-reload and change
(load-misses ()))
+ (message %s lfeats)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/12 12:55, Achim Gratz wrote:
Rainer M Krug r.m.krug at gmail.com writes:
unfortunately I still get the same message (below)
I don't see how this is possible unless one of the loaded files returns
'(nil)' instead of 't'
when loaded.
Rainer M Krug r.m.k...@gmail.com writes:
On 10/10/12 12:55, Achim Gratz wrote:
(load-misses ())) + (message %s lfeats) (setq load-misses -(delq
't + (delq 'tt
(mapcar (lambda (f) (or
OK - I get a warning when compiling:
In org-reload:
org.el:20024:19:Warning: reference
Rainer M Krug R.M.Krug at gmail.com writes:
OK - I get a warning when compiling:
In org-reload:
org.el:20024:19:Warning: reference to free variable `lfeats'
and on running org-reload afterwards an error:
call-interactively: Symbol's value as variable is void: lfeats
I don't assume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/12 14:48, Achim Gratz wrote:
Rainer M Krug R.M.Krug at gmail.com writes:
OK - I get a warning when compiling:
In org-reload: org.el:20024:19:Warning: reference to free variable `lfeats'
and on running org-reload afterwards an error:
Rainer M Krug r.m.krug at gmail.com writes:
OK - here is the output:
What is not working is re-loading of org-export-latex. How it manages to drop
the name and make nil out of this I don't know (yet). What happens if you
manually re-load org-expotr-latex?
Regards,
Achim.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/12 15:34, Achim Gratz wrote:
Rainer M Krug r.m.krug at gmail.com writes:
OK - here is the output:
What is not working is re-loading of org-export-latex. How it manages to
drop the name and
make nil out of this I don't know (yet).
Achim Gratz writes:
What is not working is re-loading of org-export-latex. How it manages to drop
the name and make nil out of this I don't know (yet).
Some files in Org provide more than one feature and at least one of
those then doesn't have a name that corresponds to the filename. It
turns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/12 18:05, Achim Gratz wrote:
Achim Gratz writes:
What is not working is re-loading of org-export-latex. How it manages to
drop the name and
make nil out of this I don't know (yet).
Some files in Org provide more than one feature and
Rainer M Krug writes:
Perfect - problem solved:
Thanks for your patience.
Successfully reloaded Org
Org-mode version 7.9.2 (release_7.9.2-432-g545166.dirty @
/home/rkrug/.emacs.d/org-mode/lisp/)
Now if you could satisfy my curiosity and tell me what you do to an
apparently freshly updated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/12 18:31, Achim Gratz wrote:
Rainer M Krug writes:
Perfect - problem solved:
Thanks for your patience.
Successfully reloaded Org Org-mode version 7.9.2
(release_7.9.2-432-g545166.dirty @
/home/rkrug/.emacs.d/org-mode/lisp/)
Now
Rainer M Krug writes:
Now if you could satisfy my curiosity and tell me what you do to an
apparently freshly updated
Org to make it dirty?
I was wondering myself...
What *can* make it dirty?
git status
should tell you what it thinks has changed.
Regards,
Achim.
--
+[Q+ Matrix-12
Rainer M Krug r.m.k...@gmail.com wrote:
On 10/10/12 18:31, Achim Gratz wrote:
Rainer M Krug writes:
Perfect - problem solved:
Thanks for your patience.
Successfully reloaded Org Org-mode version 7.9.2
(release_7.9.2-432-g545166.dirty @
/home/rkrug/.emacs.d/org-mode/lisp/)
Nick Dokos writes:
Rebasing to incorporate local patches after the pull perhaps?
No, that'd give a clean state with a different SHA-1.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and User Sound Singles for Waldorf rackAttack:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/12 18:55, Achim Gratz wrote:
Rainer M Krug writes:
Now if you could satisfy my curiosity and tell me what you do to an
apparently freshly
updated Org to make it dirty?
I was wondering myself...
What *can* make it dirty?
git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
When reloading org after update, I get the following messages in the message
buffer, where there
is apparentkly an error - but I can't see any?
Any suggestions?
Rainer
Loading /home/rkrug/.emacs.d/org-mode/lisp/ob...done
Loading
Rainer M Krug writes:
When reloading org after update, I get the following messages in the message
buffer, where there
is apparentkly an error - but I can't see any?
It's a bug in org-reload, please pull again. Thank you for the report.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron
25 matches
Mail list logo
