> Press key for agenda command (unrestricted):
> Update Org Contacts Database
> Bad sexp at line 350 in /home/simon/org/privat.org:
> (org-contacts-anniversaries "BIRTHDAY" "%y. Geburtstag %l") [7 times]
> Invalid face reference: nil [619 times]
I have the same problem, but with bddb3. The sexp t
org-exp-bibtex seems to have gone missing from git repository. Can
somebody confirm pleae.
Vikas
Hi Sebastian,
Sebastian Hofer writes:
> I'm using some of the paredit [1] functionality in org-mode, e.g. the
> deleting pairs of (),[],{}, and so forth. Note that I don't have
> paredit-mode enabled but rather use paredit-backward-delete and
> others. Recently, deleting {} as one entity stopped
Hi Sébastien,
"Sebastien Vauban"
writes:
> - html-STYLE-include-default -> html-STYLE-include-default
> (unchanged)
Fixed, thanks.
--
Bastien
Hi Simon,
thanks for reporting those problems.
Simon Thum writes:
> Press key for agenda command (unrestricted):
> Update Org Contacts Database
> Bad sexp at line 350 in /home/simon/org/privat.org:
> (org-contacts-anniversaries "BIRTHDAY" "%y. Geburtstag %l") [7 times]
> Invalid face reference:
Achim Gratz writes:
> I hope to put this together in the next week or
> so, then it will be possible to nuke all traces fr4om an old Org and
> then start from a clean slate with a new Org installation.
Okay, thanks. Let us know how it goes,
--
Bastien
Hi James,
James Harkins writes:
> I would be happy if the first setting were reduced.
What maximum size is it now? What maximum size would you like?
--
Bastien
Hi Charles,
Charles Berry writes:
> Why not use the new exporter, rather than org-babel-tangle?
A very nice example on how the new exporter can be useful!
Thanks for sharing this,
--
Bastien
Bastien altern.org> writes:
>
> Hi Rainer,
>
> Rainer M Krug gmail.com> writes:
>
> > Follow up: would it be possible to have the same mechanism for tangling,
i.e. a tag :notangle:?
> > functioning would be equivalent to property tangle: no but more visible and
consistent with the
> > :noexpo
On Mar 2, 2013 7:13 PM, "Bastien" wrote:
> > I suppose the digest could include a link to the attachment, rather
> > than replicating the entire file?
>
> We use mailman -- can you investigate and see if we can configure
> mailman to suit your needs?
It seems Achim is right. There's no option to
Alright, I solved my own problem.
I was able to get verbatim working with a unicode symbol (√) as delimeter,
by editing both org-emphasis-alist and org-export-latex-emphasis-alist.
Cheers!
--Nathaniel
On Sat, Mar 2, 2013 at 5:05 PM, Nathaniel Cunningham <
nathaniel.cunning...@gmail.com> wrote:
>
> > I have been trying to figure out how to do this. I saw Suvayu's config
> > files which he has kindly kept on github
> > (https://github.com/suvayu/.emacs.d).
> >
> > I tried to evaluate the following lines
> >
> > (add-to-list 'org-latex-classes
> > '("beamer"
> >
Hello,
Bastien
I resend a patch for HEAD of master branch.
Thanks,
Ryo.
---
* lisp/org-protocol.el: (org-protocol-convert-query-to-plist): New function.
(org-protocol-do-capture): Use new function.
When org-protocol's url has query, org-capture get query using plist-get
from store-link.
For exa
>
> You may be using an outdated version (maint branch?). Otherwise, latex
> back-end may not be loaded, but it is by default (see
> `org-export-backends').
I am using 7.9.3f updated using orgmode elpa repository. Is that a
problem?
Vikas
Michael,
Did a little research on Colemak: appears to be (1) as or even slightly
more ergonomic than Dvorak, in terms of measurable results; and (2)
designed for QWERTY users.
That said, were you a QWERTY user before you transitioned into Colemak?
. . .
Does anyone here type Russian characters?
I'd like to incorporate some scraps of code in an org file. These scraps
include both ~ and =, the markers for verbatim text and code.
I used customize-variable org-emphasis-alist to change the symbols to mark
verbatim text, but without success; adding unusual symbols broke LaTeX
export of the or
Bastien writes:
> We encourage contributors without commit access to share patches on
> the list so that everyone can review and test them.
Ignore this, I just received Jambunathan contribution on the list.
Thanks for applying it, and thanks for the patch Jambunathan.
I'm still wondering if we
Hi Nicolas,
Nicolas Goaziou writes:
>> I have added support for Freemind/Freeplane Mindmap export. I am
>> attaching sample files produced with the new exporter.
>>
>> You are welcome to merge the changes to Org repo.
>
> Done. Thank you!
We encourage contributors without commit access to shar
Bastien writes:
> It seems the ox- prefix is a bad idea, you're right.
> I'll think about it again.
Please, no. The prefix is good, you would just need to obsolete all
previously exported interfaces (autoloads and defcustoms) to this code
to either give a warning or silently "do the right thing"
Thanks for the suggestion, Eric. Following the instructions, I fired up Emacs,
loaded files of various types, then ran the command
org-html-htmlize-generate-css
Unfortunately, this resulted in an error dump:
Debugger entered--Lisp error: (error "Invalid face" popup-mouse-face)
internal-get-li
Achim Gratz writes:
> Here are two patches that fix this and implement (partly) some of your
> suggestions. I don't think Org should pollute the global Perl namespace
> by default, so I've left the definition of org-babel-perl-preface to the
> user for now. The second patch has the debugging aid
Babel: Disable wrapping
* lisp/ob-core.el (org-babel-insert-result): If the argument to ':wrap'
is 'nowrap', don't wrap the results.
* doc/org.texi (Header Arguments): Describe 'nowrap' behaviour.
This allows the results of a block to be inserted without wrapping, by
overriding a ':wrap' propert
Alan Schmitt writes:
> Rasmus writes:
>
>> Alan Schmitt writes:
>>
>> > As the order matters, as said in some replies, I prefer the
>> > AFTER_CLOSING approach.
>>
>> How can one use the a `:' in a AFTER_CLOSEing?
>
> Sorry, I don't know. I thought it was the approach you were
> suggesting.
Exp
Hello,
Jambunathan K writes:
> I have added support for Freemind/Freeplane Mindmap export. I am
> attaching sample files produced with the new exporter.
>
> You are welcome to merge the changes to Org repo.
Done. Thank you!
Regards,
--
Nicolas Goaziou
Hi Bastien,
Bastien wrote:
> "Sean O'Halpin" writes:
>
>> One small point: as we're going to have to change the meta directive
>> "#+STYLE" to "#+HTML_STYLE", can we change the name to reflect what it
>> really does in the HTML backend, i.e. insert text verbatim into the
>> element? I suggest we
Bastien wrote:
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
Then should it also support `org-export-with-tasks' variable?
>>>
>>> Yes. E.g. if `org-export-with-tasks' is set 'todo, only inline
>>> tasks with a TODO keyword should be exported.
>>
>> Done.
>
> Thanks!
Thanks!
Best rega
Hi John
On Feb 21, 2013 10:16 PM, "42 147" wrote:
> [continues off-topic]
>
> > Have you tried a Dvorak keyboard?
>
> A friend of mine ridicules me for being a QWERTY typist, but I have found
> no empirical evidence that it is actually superior. At best, it has been
> proven, in /some/ studies, t
Rasmus writes:
> Alan Schmitt writes:
>
> > As the order matters, as said in some replies, I prefer the
> > AFTER_CLOSING approach.
>
> How can one use the a `:' in a AFTER_CLOSEing?
Sorry, I don't know. I thought it was the approach you were suggesting.
> > I rely on an lco for that. To give y
Hi Sean,
"Sean O'Halpin" writes:
> One small point: as we're going to have to change the meta directive
> "#+STYLE" to "#+HTML_STYLE", can we change the name to reflect what it
> really does in the HTML backend, i.e. insert text verbatim into the
> element? I suggest we rename it to "#+HTML_HEA
Hi Alan,
Alan Schmitt writes:
> Bastien writes:
>
>> Hi Alan,
>>
>> Alan Schmitt writes:
>>
>>> To give you an idea of my setup, here it is.
>>
>> This is nice -- would you share it on Worg?
>
> Sure. Should it go there :
> http://orgmode.org/worg/exporters/index.html ?
Yes, please. Thanks,
Alan Schmitt writes:
> As the order matters, as said in some replies, I prefer the
> AFTER_CLOSING approach.
How can one use the a `:' in a AFTER_CLOSEing?
> I rely on an lco for that. To give you an idea of my setup, here it is.
> I found that with this setup I can quickly write a letter. If
Hi,
vdya...@elvees.com (Дядов Васил Стоянов) writes:
> The problem is: when I clock-in into some task and then within 1 minute
> change tasks state to DONE, information about state transition recorded
> incorrectly (:LOGBOOK: drawer is removed because of zero time, and then
> state transition rec
Hi David,
David Engster writes:
> Did you actually try that? How should Emacs possibly know that the file
> ox-icalendar provides the feature org-icalendar? This will only work if
> ox-icalendar is already loaded.
Of course, you're right. I reverted the commit.
So the problems stay. For thir
Hi Rick,
Rick Frankel writes:
> Sorry, subject didn't get properly added:
>
>
> * lisp/ob-tangle.el
> (org-babel-tangle):
> - remove un-executed attempt to ask user for file-name if
> tangling a single block (`:tangle' always has a value)
> - change handling of b
Hi Nicolas,
Nicolas Goaziou writes:
> By the way, `org-html-htmlized-org-css-url' docstring looks wrong.
> `org-export-as-org' doesn't exist anymore, neither do "batch mode".
>
> So, is the variable still useful? If it is, could someone could fix its
> docstring so it reflects what is really hap
Alan Schmitt writes:
Michael Strey writes:> Rasmus,
>> In fact to use the scrlttr2 support in Org I had to adjust a LCO files
>> because it's currently loaded after LATEX_HEADER arguments (so all
>> customization was overwritten). I didn't like that.
>
> After this remark I checked my changes
Michael Strey writes:> Rasmus,
>> In fact to use the scrlttr2 support in Org I had to adjust a LCO files
>> because it's currently loaded after LATEX_HEADER arguments (so all
>> customization was overwritten). I didn't like that.
>
> After this remark I checked my changes and compared them with
Bastien writes:
> We use mailman -- can you investigate and see if we can configure
> mailman to suit your needs?
I don't think that it is possible to remove attachments specifically for
the digest, much less replacing them with links. But the digest can
have a maximum size set, which triggers se
Nicolas Goaziou writes:
> The infloop should be fixed. Thank you.
Thank you. I've just pushed a fix so that the new exporter is loaded
during batch testing. This results in four so far unreported test
failures:
4 unexpected results:
FAILED test-org-table/references/format-specifier-E
FAI
Hi all,
I'm using some of the paredit [1] functionality in org-mode, e.g. the
deleting pairs of (),[],{}, and so forth. Note that I don't have
paredit-mode enabled but rather use paredit-backward-delete and others.
Recently, deleting {} as one entity stopped working, but it still works for
[] and
Hello,
Achim Gratz writes:
> Probably due to some recent changes by Nicolas, current master infloops
> on the test following these (i.e. that would be test 98):
>
> […]
>passed 94/365 ob-tangle/no-excessive-id-insertion-on-tangle
>passed 95/365 ob-test/org-babel-combine-header-arg-
Hi all,
I've updated to recent master to fix a problem the new exporter fixes in
master. I didn't update for a few months, so it's not easy to tell when
things broke. I already looked for solutions, but could not find any for
the below. Please help me track these down.
I observe four problem
Bastien writes:
> Hi David,
>
> David Engster writes:
>
>> (eval-after-load "org-icalendar"
>> '(error "The old org-icalendar exporter is deprecated; use
>> ox-icalendar instead."))
>
> I'm not sure about this one: where are you suggesting to add this?
> In org.el?
Your call. Anywhere where it'
Nicolas Goaziou writes:
> Bastien writes:
>
>>> Then should it also support `org-export-with-tasks' variable?
>>
>> Yes. E.g. if `org-export-with-tasks' is set 'todo, only inline
>> tasks with a TODO keyword should be exported.
>
> Done.
Thanks!
--
Bastien
Bastien writes:
>> Then should it also support `org-export-with-tasks' variable?
>
> Yes. E.g. if `org-export-with-tasks' is set 'todo, only inline
> tasks with a TODO keyword should be exported.
Done.
Regards,
--
Nicolas Goaziou
Hi Nicolas,
Nicolas Goaziou writes:
>> So I support Sébastien's idea here: :noexport: should remove
>> inline tasks from the exported string. Maybe we need to set the
>> `org-export-filter-inlinetask-functions' at some point to support
>> this?
>
> Then should it also support `org-export-with
Hello,
Bastien writes:
> From on intuitive point of view: Inline tasks support tags, and
> :noexport: means "Don't export me", me being whatever is tagged.
>
> So I support Sébastien's idea here: :noexport: should remove
> inline tasks from the exported string. Maybe we need to set the
> `org
Bastien writes:
> Hi Alan,
>
> Alan Schmitt writes:
>
>> To give you an idea of my setup, here it is.
>
> This is nice -- would you share it on Worg?
Sure. Should it go there :
http://orgmode.org/worg/exporters/index.html ?
I'll send you my ssh key.
Alan
Hi Christopher,
Christopher Schmidt writes:
> Unfortunately I see is no other easy way to reproduce this.
Well, I doubt anyone will have time to reproduce this before
Org 7.9.4 and I'd rather concentrate on Org 8.0 for now, so...
> (I am fine with wontfix in maint.)
... most probably this wil
Hi Zech,
Not To Miss writes:
> I know C-u C-c C-v t tangles current code block only, even if there
> are other code blocks that have the same tangle file name. Isn't it
> counterintuitive? It makes more sense that this command tangles all
> the code blocks that belongs to the same file, in my op
Hi Andreas,
Andreas Leha writes:
> thanks for taking this up! But I am not sure, whether I like the
> current implementation too much. Instead of saving the org-file itself,
> I'd prefer the org-file to be auto-saved.
You can use auto-save-mode then.
I changed the `buffer-auto-save-file-name'
Hi Achim,
Achim Gratz writes:
> So I'll cut the changelog after the first sentence and relegate the rest of
> the
> explanation to the commit message (if the patch works, of course) -- OK?
Yes. Feel free to add all the useful information in the git
commit log, after the Emacs-ready change log
Steve Purcell writes:
> No backtrace, and just a small rendering quirk: the "_" in the bare
> URLs is escaped with a backslash in the resulting HTML.
>
> That should be a trivial fix. :-)
Crossing fingers :)
--
Bastien
On 2 Mar 2013, at 12:09, Bastien wrote:
> I meant the HEAD of the maint branch, from the Org-mode git
> repository.
>
> Does anyone with a local install of Org can reproduce this bug?
Ah, yes -- that seems to work better.
No backtrace, and just a small rendering quirk: the "_" in the bare URL
Torsten Wagner writes:
> Now I make a tiny change e.g. change the length of the appointment from within
> SOGo and sync back I get
>
> TODO TODO Neuer Termin mit Foo und Bar r<2013-03-06 Wed 10:00-11:00>
> :PROPERTIES:
> :ID: 8a9651c0-faee-4416-afa6-979e328a3d15
> :END:
>
> As you
Bastien writes:
> Hi David,
>
> David Engster writes:
>
>> The most serious issue is that things will often seem to work because
>> old exporters are pulled in from Emacs, possibly *very* old
>> exporters.
>
> I've added (provide 'org-icalendar) to ox-icalendar.el so that
> a user will load the co
Probably due to some recent changes by Nicolas, current master infloops
on the test following these (i.e. that would be test 98):
[…]
passed 94/365 ob-tangle/no-excessive-id-insertion-on-tangle
passed 95/365 ob-test/org-babel-combine-header-arg-lists
failed 96/365 org-missing-de
Hi Steve,
Steve Purcell writes:
> On 2 Mar 2013, at 11:22, Bastien wrote:
>>
>> I cannot reproduce this with the current maint HEAD and emacs -Q.
>>
>> Can you? Let us know, thanks,
>
>
> Well, I have a clean Emacs HEAD build as of the following commit,
> and it still fails with -Q:
I meant
On 2 Mar 2013, at 11:22, Bastien wrote:
>
> I cannot reproduce this with the current maint HEAD and emacs -Q.
>
> Can you? Let us know, thanks,
Well, I have a clean Emacs HEAD build as of the following commit, and it still
fails with -Q:
Author: Glenn Morris
Date: Sat Mar 2 06:17:34 2013
Hi Steve,
Steve Purcell writes:
> Using the org-mode included in Emacs HEAD as of yesterday, the following
> content causes an error when exporting as html:
I cannot reproduce this with the current maint HEAD and emacs -Q.
Can you? Let us know, thanks,
--
Bastien
Hi David,
David Engster writes:
> (eval-after-load "org-icalendar"
> '(error "The old org-icalendar exporter is deprecated; use ox-icalendar
> instead."))
I'm not sure about this one: where are you suggesting to add this?
In org.el? Will the users get the warning if org-icalendar.el has
bee
Hi David,
David Engster writes:
> The most serious issue is that things will often seem to work because
> old exporters are pulled in from Emacs, possibly *very* old
> exporters.
I've added (provide 'org-icalendar) to ox-icalendar.el so that
a user will load the correct file instead of the old
Hi Marc-Oliver,
Marc-Oliver Ihm writes:
> find a new version of org-favtable.el attached and on worg.
if you want to have org-favtable.el in contrib/lisp/ please
let me know. It'd be nice to have a Worg page describing what
it does exactly: extracting some of the comments you have in
the sourc
Hi Sébastien,
"Sebastien Vauban"
writes:
> FYI, there's a bug (not related to this change): if you filter out some events
> (for example, a "work" meeting today, with an active timestamp) by tag (show
> only "home" related things), you don't see the event headline, but well the 5
> first entry t
Hi Rainer,
Rainer M Krug writes:
> Follow up: would it be possible to have the same mechanism for tangling, i.e.
> a tag :notangle:?
> functioning would be equivalent to property tangle: no but more visible and
> consistent with the
> :noexport:? One could also define properties to be tangled
Hi Daniel,
Daniel Hawthorne writes:
> Hi all, I'm having trouble with the inline image feature. The displayed image
> doesn't update. In fact, all the images display an identical image regardless
> of
> the link path. Export works fine, so its something specific to inline
> image. Clearing the
Hi Nick,
Nick Dokos writes:
> However, the formula without the @ in front of III *also* works in this
> case. I don't know whether that's an accident or intended behavior.
FWIW, I don't know neither... maybe Carsten can tell.
--
Bastien
Hi Alan,
Alan Schmitt writes:
> To give you an idea of my setup, here it is.
This is nice -- would you share it on Worg?
Thanks!
--
Bastien
Hi James,
James Harkins writes:
> I suppose the digest could include a link to the attachment, rather
> than replicating the entire file?
We use mailman -- can you investigate and see if we can configure
mailman to suit your needs?
--
Bastien
Hi Sébastien,
"Sebastien Vauban"
writes:
> I think we should see the 8 of March as reference date for fixing the start
> date (or length, depending on how we see it) of the warning delay.
That's now the case, thanks for reporting this.
--
Bastien
Hello,
Simon Campese writes:
> thanks a lot for the patch. It partly works, as long as there are some
> more characters after the first comma, but a single comma at the beginning of
> a line still gets purged. Now we can start discussing about whoever
> would want to have a single comma in a lin
71 matches
Mail list logo
