Achim Gratz writes:
> Nicolas Goaziou writes:
>> That may not solve the problem, but could at least simplify it.
>
> The problem can be demonstrated with just this code snippet in place of
> org-export.el:
[...]
> So it might be a bit easier to solve now (I hope).
This cod
Daniel Hawthorne writes:
> As stated by the variable "org-version," the git repo version is
> 7.8.03.
Each checkout you make from the repo has it's own version. Now, if you
are shown version 7.8.03, it can mean several things: you really have
that version checked out (forgot to pull? on a dif
Nicolas Goaziou writes:
> I think you can go ahead and commit it: your description of the problem
> will be more accurate than mine.
>
> Thank you for this investigation and, obviously, for the fix.
You give me too much credit here... the patch fixes things in that it
will now consistently compile
[re-sent]
John Hendy writes:
> I typically use orgmode + babel on Linux and have no problems. Trying
> to run on Windows 7 and having issues...
>
> (setq org-babel-R-command "C:/Program\ Files/R/R-2.15.0/bin/R")
Try the 8.3 compatible name to avoid the space in the path. If it ever
goes through
John Hendy writes:
>> (setq org-babel-R-command "C:/Progra~1/R/R-2.15.0/bin/R")
>
> Same error. Also, curiously, =M-x customize-variable RET org-babel-R
> TAB= yields no results... is this the right variable?
That variable doesn't seem to have acustomize interface. Might be worth
a bug report.
I
Nicolas Goaziou writes:
> Ok, I misunderstood your answer: I thought you had solved the problem.
I thought that too at first, but it didn't survive closer scrutiny...
>> I'm not sure what you intended the macroexpansion to be at the place
>> of use, hence my suggestion to check these macros again
Thorsten Jolitz writes:
> when I try to use the new exporter outside of an Org buffer, e.g. from a
> function or with M-:, it seems that there is a problem with the current
> buffer that is used for exporting - it is not the buffer of the Org file
> given as argument.
You should read the docstrin
Nicolas Goaziou writes:
> I will look more carefully at the `org-export-with-current-buffer-copy'
> macro, but, since I cannot reproduce the compilation error it may be
> hard to find the mistake.
After some consideration, I think this is what the macro should look
like:
--8<---cut he
Nicolas Goaziou writes:
> Not exactly. With this version, symbols generated with gensym are never
> used, and the macro isn't hygienic anymore.
Yeah, I missed out on some commas along the way and it probably needs
double quoting (which I was trying to avoid). The first version interns
the gensyme
SW writes:
> Library is file /usr/share/emacs/23.2/site-lisp/org-mode/org-install.elc
That is a completely borked installation (not your fault quite likely),
org-install.el should never be byte-compiled. I see Sebastien is the
package maintainer, it would be nice if this (and actually a few other
Giovanni Ridolfi writes:
> 4. Then I run emacs:
> (as suggested in http://orgmode.org/worg/org-hacks.html
>>c:\Users\me\programs\emacs\bin\emacs.exe -batch -Q -L lisp -l
>>org/UTILITIES/org-fixup.el --eval '(org-make-org-version "7.8.11"
>>"c75120aa71257" "blabla")'
> but the command ended wi
er from the scratch buffer or the command line. I'll update org
hacks with the instructions when you have installed the patch.
>From 5805109804bc55ef6bf079366dfd24fb928377c3 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Wed, 11 Jul 2012 19:32:33 +0200
Subject: [PATCH] Let the us
Bastien writes:
> Achim Gratz writes:
>> I'll update org
>> hacks with the instructions when you have installed the patch.
>
> I just installed the patch, thanks.
Documentation on WOrg is updated to reflect the new reality...
:-)
Regards,
Achim.
--
+<[Q+ Matrix-1
Giovanni Ridolfi yahoo.it> writes:
> that does not work. )-:
Instead of doing what is said in the document you keep inventing your own
invocations. Why not simply follow the instructions? Hint: "org" is not the
same as "..", so substituting one for the other isn't going to work. You have
to c
The corresponding defvar should probably be moved:
In org-clock-in:
org-clock.el:1208:53:Warning: reference to free variable `org-clock-out-time'
In org-clock-in-last:
org-clock.el:1264:31:Warning: reference to free variable `org-clock-out-time'
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305
Current testing results with the exporter files uncompiled:
2 unexpected results:
FAILED test-org-export/read-attribute
FAILED test-org-export/unravel-code
...and compiled:
6 unexpected results:
FAILED test-org-export/read-attribute
FAILED test-org-export/table-cell-alignment
Nicolas Goaziou writes:
> In fact, I do get the errors from a "make test" but I don't know how to
> reproduce them from emacs.
For starters you could try to run Emacs like "make test" does, but
remove "-batch". This error somehow seems to involve that the test
always returns "'left 'left 'right"
Bastien writes:
>> The corresponding defvar should probably be moved:
>
> Done, thanks.
Another issue: the key binding doesn't work, since "C-C C-x C-i" and
"C-C C-x C-I" are both mapped to org-clock-in-last via a general key
mapping of "S-TAB" to "TAB". I can't seem to find where this mapping is
Nicolas Goaziou writes:
> It looks like table-cells have a wrong `:parent' property when
> org-element.el is byte-compiled. In `org-element-table-cell-parser',
> replacing backquote with `list' solves the problem.
>
> This is related to modifications by side-effect of list elements, but
> I don't
Nicolas Goaziou writes:
> This is related to modifications by side-effect of list elements, but
> I don't know why it only happens when the file is byte-compiled and why
> it only focus table cells.
I just see that you fixed this. Congratulations and thank you!
Regards,
Achim.
--
+<[Q+ Matrix-
Nicolas Goaziou writes:
> Unfortunately, there's now an
>
> "(invalid function org-export-with-current-buffer-copy)"
>
> error when using make test
Not for me... how do you have the build and the test configured?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Bl
At long last the promised documentation for the build system starts to
materialize on Worg:
http://orgmode.org/worg/dev/org-build-system.html
It undoubtedly needs improvement, so please let me know where and/or add
to it yourself. Thank you.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neu
Nicolas Goaziou writes:
> I hard-link org-element.el and org-export.el in lisp/ and I use the
Ditto, to be exact:
rm -f lisp/org-{export,element,e-*}.{el,elc}
ln contrib/lisp/org-{export,element,e-*}.el lisp/
> following local change to default.mk (I know I should be modifying
> local.mk instead
Nicolas Goaziou writes:
> I hard-link org-element.el and org-export.el in lisp/ and I use the
> following local change to default.mk (I know I should be modifying
> local.mk instead, but this was easier to do).
Since this has come up before: _please_ do not change anything in
default.mk, especiall
Nicolas Goaziou writes:
>> 2 unexpected results:
>>FAILED test-org-element/parent-property
>>FAILED test-org-element/set-element
>
> I cannot get those. Have you tried with a recent Org (i.e. post
> 95cd07d058da79cb1767946dba6e4b9128a3a702)?
I used whatever I had pulled yesterday... agai
Nick Dokos writes:
> In my case, make up2 installed into
>
> /usr/share/emacs/site-lisp/org
You can always check what make thinks it should do via
make config
or even
make config-all
> (add-to-list 'load-path "/usr/share/emacs/site-lisp/org")
That is not necessary, at least if subdirs.el
Suvayu Ali writes:
> See the output of "make help". The above is not the prescribed way to do
> it. If you want the old make behaviour, you can do "make oldorg && make
> install".
No, he's using the latest release version of Org, which means the old
Makefile (if this was really his intention I#d r
James Harkins gmail.com> writes:
> So, how do I solve the problem with org-version?
I already sent an answer to your original question, but somehow that didn't make
it to the list: most likely you've missed a "(require 'org-install)" in your
startup sequence.
Regards,
Achim.
Nicolas Goaziou writes:
>> compile::
>> $(CP) contrib/lisp/org-{export,element,e-*}.el lisp/
>
> Noted. Thank you.
That should be "all compile::", really.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Str
Vladimir Lomov writes:
> Begining from some revision (I don't remember exact revno) function
> `flet' was declared obsolete so Org-mode compilation is accompanied with
> warnings about that.
>
> If just ignore them then I get malfunction Org-mode. I made patch to
> change all `flet's to appropriate
Eric Schulte writes:
> This attached alternate patch introduces two new compatibility macros
> named `org-flet' and `org-labels' in org-macs.el. These macros are
> aliased to the appropriate cl macro depending on the version of Emacs in
> use.
Wouldn't you want to use defmacro instead of defalias
[re-sent due to no-show on the list... sorry if you get it twice]
Nicolas Goaziou writes:
> Nevermind: I fixed them. I think all tests should pass now, in both
> emacs 24 and emacs 23.
Yes!
> If you confirm this, I will move org-element.el into core.
Go ahead... and let us all celebrate that mo
Eric Schulte writes:
> Why? Using `defalias' seems simpler because with `defmacro' I would
> have to copy the macro arguments and stub out a trivial macro body.
> Also, this way the version check only happens once (at load time),
> rather than every time the macro is called.
I confused defalias a
diff --git a/contrib/lisp/org-e-ascii.el b/contrib/lisp/org-e-ascii.el
index 1851273..a9551af 100644
--- a/contrib/lisp/org-e-ascii.el
+++ b/contrib/lisp/org-e-ascii.el
@@ -1100,7 +1100,7 @@ (defun org-e-ascii-horizontal-rule (horizontal-rule
contents info)
"Transcode an HORIZONTAL-RULE objec
Vladimir Lomov writes:
> Thanks, would work fine with this small change:
Thanks, but please do not patch a patch file...
Eric, that leaves:
In org-babel-edit-distance:
ob.el:624:37:Warning: function `map' from cl package called at runtime
which the byte-compiler did not pick up on before. If i
Eric Schulte writes:
> Okay, I've noticed a number of these errors as well. It looks like the
> old version of flet allowed the definition of recursive functions, but
> the new cl-flet does not.
The defalias checks for the wrong Emacs version. I've just built
another Emacs24 which got version 24
Eric Schulte writes:
> I also applied another patches fixing the other cl related build issues
> mentioned by Achim. The build now succeeds on the latest Emacs without
> generating any warnings and all tests pass (although it sounds like we
> could use more test coverage).
I don't think d7a8b6636
>From 61310146053cff23972d8926c73d0eedae157190 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Wed, 25 Jul 2012 19:09:08 +0200
Subject: [PATCH] Let ob-C and ob-fortran work correctly on Windows/Cygwin
* lisp/ob.el (org-babel-exeext): New defconst to hold extension for
executables or nil
Robert Louis McIntyre writes:
> This only happens when using emacs in batch mode.
>
> I've created a minimal example that demonstrates this
> problem at:
>
> http://aurellem.org/dl/possible-org-bug.tar.bz2
I'm getting the same error both in batch and in non-batch mode for Emacs
23.3 and in non-ba
Achim Gratz writes:
> This looks to be either a bug in font-lock or some missing setup for it
> to work correctly, maybe just for Java; or java-mode (which is based on
> cc-mode) tries to use facilities that aren't present in batch; or
> cc-mode has a bug in version 5.32.2 that
Eric Abrahamsen writes:
[...]
> GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.11)
> of 2012-07-23 on pellet
> 7.8.10
Given that Emacs 24.1.50 ships with Org 7.8.11, why are you still on
7.8.10?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Eric Abrahamsen writes:
>> Given that Emacs 24.1.50 ships with Org 7.8.11, why are you still on
>> 7.8.10?
>
> Good question! Given that I keep up with the development version of
> org-mode, it's an even better question. And yet… I updated org from git
> ten minutes ago,
Well, then you miss a:
gi
Bastien writes:
> The snapshot is created by gitweb on the fly.
I'm not talking about those — yes, they should be what's in Git's index,
nothing more or less. I was thinking of org-latest.{zip,tar.gz}, which
might usefully include the autoload files or even byte-compiled
sources. So we would hav
Markus Baden writes:
> I just installed org-mode via the recipe provided with the current
> development version of el-get [1]. Org-Mode is installed correctly
> into emacs.d/el-get/org-mode and the docs can be found in the doc
> subfolder. The recipe [2] adds the doc to the info via the :info "doc"
Greg Minshall writes:
> install-info(doc/org): replacing existing dir entry for `org'
> cp: /var/backups/infodir.bak: Permission denied
> install-info(doc/org): couldn't backup /Users/minshall/usr/share/info/dir in
> /var/backups/infodir.bak: Inappropriate ioctl for device
What does 'install-info
Alan Schmitt writes:
> François Allisson writes:
> It works great with one caveat: it's calling "sudo" to do the "make
> install". As I install locally, I don't want to use sudo. Is it possible
> to configure something in local.mk to do this?
SUDO = # nothing, really
There's a comment in default
Greg Minshall writes:
> here's the install-info version. (i'm afraid i wasn't aware that
> install-info was a local utility; i assumed it was part of the build
> system for org or ...)
This is indeed dpkg's version of install-info and a very old one to boot
(apparently from macports?). First off
Kyle Machulis writes:
> In commit abbea596111611a945d73783b3e8790e76599740, the commit message
> starts with
>
> - Move org-element.el from contrib/lisp to lisp/.
>
> However, it looks like org-element.el just got deleted, not moved.
> This causes much badness when trying to rebuild.
Thanks for re
Neuwirth Erich univie.ac.at> writes:
> 7 unexpected results:
>FAILED ob-fortran/command-arguments
>FAILED ob-fortran/fortran-var-program
>FAILED ob-fortran/input-var
>FAILED ob-fortran/list-var
>FAILED ob-fortran/list-var-from-table
>FAILED ob-fortran/preprosessor-var
Torsten Wagner writes:
> One Idea I had and which was mentioned by Rasmus already too, would be
> to use the same property block but being able to hide certain
> properties
>
> #+ HIDE_PROP: ID, UUID, ODF_PROP, MOBILE_ORG_PROP
I don't think that moves us into the right direction...
Let me again s
Olaf Meeuwissen writes:
> Or install Ubuntu's separately packaged org-mode package. The emacs23
> package on Ubuntu and Debian ships with the bundled org-mode version
> (6.33, IIRC). The org-mode package is significantly newer, 7.x. The
> only glitch I've encountered is with accessing the info p
Bernt Hansen writes:
> Or just use two drawers... PROPERTIES and SYNCDATA (or some other
> appropriate name) so you unfold the on you care about and leave the
> other folded. That seems a lot simpler than stops in drawers...
It might seem to, but I'm actually using this right now (LOGBOOK and
CLO
Neuwirth Erich univie.ac.at> writes:
> Are the tests supposed to work only from within Emacs?
No, but you might be in a better position to tell us what went wrong, as you
still haven't shown what error you are getting from the tests in question.
So could you please go into the org directory and
I'm currently seeing a problem with this test (only on Win7, both
NTEmacs and Cygwin). The test just hangs and never finishes. All my
attempts to have it fail in the same way in an interactive sessions were
fruitless. However, it seems that the first time a session is
initiated, it does not sta
Achim Gratz writes:
> I'm currently seeing a problem with this test (only on Win7, both
> NTEmacs and Cygwin). The test just hangs and never finishes. All my
> attempts to have it fail in the same way in an interactive sessions were
> fruitless. However, it seems that the fir
Luis Anaya writes:
> Bastien writes:
> Ok... my bad... pilot error... missing (require 'org). I would've
> thought (org-install) would've loaded it. Anyway, this solved the
> problem by adding the require on my .emacs file.
You've just hidden the real problem, which seems to be a missing
(require
Eric Schulte writes:
> There are a number of tests which execute shell code blocks in
> test-ob.el. This file has no guards, so it will be run on every
> system.
I know, I'm not (currently) talking about these. What puzzles me is
that the three tests in test-ob-sh get defined and run even though
Neuwirth Erich writes:
> I do (of course) have /bin/bash and the error is produced by bash.
OK, so the linebreaks have been corrupted in your original post. You
actually got two error messages it seems:
>>> i686-apple-darwin11-gfortran-4.2.1: error trying to exec 'cc1':
>>> execvp: No such file
Luis Anaya writes:
> In org-toggle-heading:
> org.el:19364:26:Warning: attempt to let-bind constant `org-outline-regexp-bol'
Are you using Emacs23? Because I don't get these on Emacs24 and they
look positively wierd...
Plus, it's one of those instances where it seems to make a difference in
which
Achim Gratz writes:
> In any case, the interaction between org and org-element needs a
> serious overhaul and while we're at it this work should be extended to
> other subsystems of org.
I've just pushed two new make targets to master that will compile org
with a single Ema
Bastien writes:
> Yes. The whole maze needs a treat. Please submit a patch if you feel
> like undertaking this task. I managed to get zero warnings with Emacs
> 24.1 and did not take the time to check with Emacs 23.
That is going to be one big hairy patch that touches almost everything.
Maybe i
Bastien writes:
> All right. If useful, please push a public branch for this on
> orgmode.org. I will try downloading Emacs 23 and see what warnings
> will have here.
Done, branch name is "Globals". Merge it fast or be prepared for tons
of merge conflicts. I already resolved the ones created b
Johan Ekh writes:
> git pull
> error: Unable to find 16d23c07dd3697db790b14e6873c65404c912e3f under
> http://repo.or.cz/r/org-mode.git
> Cannot obtain needed object 16d23c07dd3697db790b14e6873c65404c912e3f
> error: Fetch failed.
Check the files in .git/objects/pack — delete those *.idx files that
Achim Gratz writes:
> I'm currently seeing a problem with this test (only on Win7, both
> NTEmacs and Cygwin). The test just hangs and never finishes. All my
> attempts to have it fail in the same way in an interactive sessions were
> fruitless. However, it seems that the fir
Steinar Bang dod.no> writes:
> I pulled org-mode master from git today. When I tried to open an org
> file, it failed, with the following message in the minibuffer:
> File mode specification error: (invalid-function org-check-version)
My guess is that you have outdated autoloads... but please f
I've just pushed a change to the Makefile to more easily allow
customization of compilation methods. See
http://orgmode.org/worg/dev/org-build-system.html#sec-3-2-1
for what is available.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations
Mikhail Titov writes:
> I'm running Org-mode version 7.8.10 (release_7.8.10-658-g451191.dirty)
No you don't... please do
git fetch --tags origin
Can't help with your question, sorry.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implemen
Bernt Hansen writes:
> Tangling doesn't work for me in git master anymore. Git bisect
> identifies the following commit as introducing the problem
[...]
> Debugger entered--Lisp error: (void-function letrec)
> (letrec ((intersect ...)) (funcall intersect (case context ... ... ...)
> (split-stri
Bastien writes:
> Please make the default "make" procedure display all warnings that the
> user would see by compiling Emacs itself.
That isn't even possible, you'd need to use Emacs' build system (which,
btw gives inconsistent results for repeated compiles).
> I know we disagree about this: you
Eric Schulte writes:
> But we certainly shouldn't (and currently aren't?) inhibit the display
> of any warnings when the default make is run. I was surprised to run
> make compile-source and see additional warnings which weren't shown
> during regular make.
These warnings aren't reliable — the by
Bastien writes:
> One thing I need to understand: what are the warnings that you have
> when compiling within a single process and you don't when compiling
> with one process per file?
Emacs Lisp as a dynamic language has no concept of a "well-formed"
program that can be verified by just looking a
Bastien gnu.org> writes:
> Please give me an example of a warning that is shown while compiling
> within a single Emacs process and not shown while compiling files with
> one Emacs process per file.
I don't know if something like that currently exists, if you want to check set
_COMPILE_=slint2 an
Bastien gnu.org> writes:
> ~$ emacs -batch -Q --eval "(byte-compile-file
\"~/install/git/org-mode/lisp/ob.el\")"
>
> I get warnings in the second case, not in the first case.
You should, because the command line you use does not set up the load-path
correctly. The requires will now use the stan
Bastien writes:
> Do you get them with make
> ~$ make _COMPILE_=single
Not now, but I've seen them before. I think this is one of those cases
where an indirect require provides a dependency.
> How do you set up the load-path
The current directory (which is lisp) is prepended to the load-path
Bastien writes:
> However, I would suggest these changes to the current default.mk:
These changes do not belong into default.mk — default.mk is the fallback
for when no changes to local.mk have been made.
> - Have a target `make single' (useful for developers)
>
> - `make elint' would run the cur
Eric Schulte writes:
> I don't find the strings "single compile", "compile-source" or "elint"
> anywhere in the Org documentation. Perhaps there is different
> documentation for the Makefile?
Yes, as mentioned several times in this thread:
http://orgmode.org/worg/dev/org-build-system.html
I'll a
Eric Schulte writes:
> I second the idea that a top level 'make elint' would be very useful for
> developers (see the attached patch).
I'll see to implement that when and if I get elint to process the Org
sources without throwing bogus warnings and errors because it runs into
some depth limit. Un
Suvayu Ali writes:
> On Sun, Aug 12, 2012 at 10:09:31PM +0900, Waldemar Quevedo wrote:
>>
>> Not a big deal but I see that you have to set os-github-auth and call M-x
>> os-import, os etc..
>> to use org-sync. Since the library is named org-sync, wouldn't it be better
>> to
>> base on the librar
Here's what my investigations into the elint make target(s) have dug up
so far…
I've increased max-specpdl-size and max-lisp-eval-depth by more than a
factor of ten. Emacs will now eat a good deal of memory, and a few
errors have been dodged this way, but whenever elint encounters
cal-menu, Emac
Bastien writes:
> I'll stick to this: it is good to document all existing targets.
>
> The question is whether a target should be displayed by `make helpall'
> rather than just ̀make help'.
As long as `make helpall´ was all the documentation that meant it had to
look like it does.
Regards,
Ach
Bastien writes:
[...]
> I hope you'll understand the choices above.
You should know the answer from the previous discussion, but I've
clearly failed to reach you. Given your obvious desire to take over
direct control of the further development of the build system, I won't
do any further developme
Eric Schulte writes:
> Ugh, this is more headache related to the renaming of all cl-* functions
> between the released version of Emacs 24 and the development head of
> Emacs (which I'm using). I've just pushed up a change after which all
> tests are passing on both the development head and the re
Bastien writes:
> Please heavily test the current HEAD of the git repository.
> If you have bugs that you didn't send to the list, please do
> it now.
I get these test fails with Emacs 24.1, 24.2-rc (but not on 24.1.50 or
24.2.50, although the latter activates only 214 instead of 371 tests,
which
Marius Hofert writes:
> I found http://orgmode.org/worg/org-dependencies.html and proceeded as
> described
> there to set up texi2dvi for LaTeX export. I don't have the egrep bug
> mentioned,
> so all I had to do was:
>
> 1) put this in ~/.emacs:
>(setq org-latex-to-pdf-process "texi2dvi -p %
Nick Dokos writes:
> I fixed that on worg.
Thanks.
> I added this comment to worg as well, but note that the setqs need the '(...)
> treatment.
Too much copy and paste... again it should be customized, not setq'd
anyway.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromed
Ken Williams writes:
> I'm on Cygwin, is that not a supported testing configuration maybe?
Then why don't you use Cygwin's Emacs? Or read this:
http://orgmode.org/worg/dev/org-build-system.html#sec-3-1-4
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Jambunathan K writes:
> (Sometime back, I had made a request to Achim to
> port my ELPA changes to the new build system. I hope it is in his TODO
> list. Achim, are you there?)
These changes are just what's in 395098f6f1 or is there more?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron
Jambunathan K writes:
> Mainline version
>
> 1. Doesn't update `archive-contents' which is necessary in order to
>browse packages in the repo with `list-packages'. My private version
>does it with `package-upload-file'.
That's the right place to do it, so that'll be implemented with the
Karl Voit writes:
> On my system [3] I notice 100% load on one of my two cores when
> Emacs is generating the agenda views. So I am not sure whether more
> cores could increase the performance. Probably a faster CPU? Is
> there something that makes Emacs use multiple cores in parallel?
No, Emacs i
kg.el'. (Note the `-pkg.el')
It's not pushed to the orgmode repository yet. Please have a look at
the ELPA tar produced with the following patch (after including
UTILITIES/server.mk from your local.mk):
>From 0bf94de6edfa99a1f47dedbb9ccbbde44417c259 Mon Sep 17 00:00:00 2001
F
Nicolas Goaziou writes:
> In a recent commit, I've modified `org-table-number-regexp' so it can
> recognize numbers with a comma as the decimal mark by default.
This should really follow the definitions in the locale...
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XT
Jambunathan K writes:
> I added the diff below to Makefile and did a
> $ make elpa
I said edit local.mk... :-) Really, leave Makefile alone.
> Quick comments: It is far from OK.
Close enough for me.
> 1. The bundle is a tar file not tar.gz file.
I hadn't considered that package manager ca
Bastien writes:
> If there are users of older Emacsen here, please pull from the
> git repo and report any problem in compiling and running Org.
Emacs 23.2 on openSuSE compiles and tests OK (except for the babel
sh-session test that I reported earlier, but that only seems to affect
batch mode).
I just realised that there's a trainwreck in the making:
We have org-e-man and org-man in contrib. Now when the exporter moves
into core, org-e-man supposedly changes its name to org-man as
well... not good. Since org-man was there first, could org-e-man be
renamed to something that will not co
Luis Anaya writes:
> I have no problems. We can rename org-e-groff.el to org-groff-mm.el and
> consequently, org-groff-man.el ? If I get hold around the MOM macros, I
> can then name them org-groff-mom.el
Well, if the org-e-* stuff gets renamed to oe-* instead it becomes a
non-issue plus it would
Pierfranco Minsenti writes:
> The symbol of a square appears instead of accented letters.
The most likely explanation is that the font you are using isn't
includig those code points. Try a different font.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Bastien writes:
> But then archiving the "* Make tea" headline would require to merge the
> logs of the archived one and those of the alive one. Quite some work.
How's the merge driver for Git coming along? Archiving to Git would be
a really welcome feature, I guess.
Regards,
Achim.
--
+<[Q+
Loris Bennett writes:
> Obviously I could simply learn elisp and do this myself, as described in
> the manual, but has anyone already implemented a link type to an emacs
> fileset?
[[elisp:(filesets-open nil "bla")][Fileset: bla]]
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb
Eric Schulte writes:
> Will the new ELPA package include org-element.el and org-export.el, or
> would those require separate packaging?
The ELPA archive does not include aynthing from contrib/. So, org-element is
included, but not org-export.
However, one of the last-minute changes to the build
Andy Schönemann writes:
> I just upgraded to org-mode 7.9 and I want to test the new
> org-notify.el package. I inserted the two lines (require 'org-notify)
> and (org-notify-start) into my init file. But I can't use this
> mode.That means I can't run none of the commands with M-x
> org-notify-*.
301 - 400 of 1726 matches
Mail list logo
