Re: [O] ob-lua
Hello, Thibault Marin writes: > I am attaching an updated patch adding the Lua language to the CSS in > `org-html-style-default'. Patches applied. Thank you. Would you consider signing FSF papers if not already done? Regards, -- Nicolas Goaziou
Re: [O] BUG: swapped utf-8 symbols in org-entities
Hi Nicolas, Sorry for the late reply. Am I supposed to send the patch against master or against maint? If against master, see the file starting at 0001. If against maint, see the file starting with 0002. For some reason, I can't apply the 0001 patch to the maint branch either, nor can I rebase it to the maint branch... Weird. Hopefully this is good enough. Best, Kosta -- Konstantin Kliakhandler http://slumpy.org )°) )°( (°( On 5 July 2016 at 22:13, Nicolas Goaziou wrote: > Hello, > > Konstantin Kliakhandler writes: > > > I have an additional, similar patch - In this one I changed the unicode > > symbol for \circ from something looking like ^ to [image: \circ] (#x2218 > = > > "ring operator" = \circ in TeX input method). > > For some reason, I'm unable to apply it to maint branch. Could you > rebase your repository and try again? > > Thank you. > > Regards, > > -- > Nicolas Goaziou > 0001-org-entities-Correct-unicode-symbol-of-circ.patch Description: Binary data 0002-org-entities-Correct-unicode-symbol-of-circ.patch Description: Binary data
Re: [O] Emacs movement keys
> You know you're an Emacs user when... You select some text in MS Word and Type C-w to cut it... and are very unhappy when Word closes... > > you try to get to the beginning of line and find yourself selecting > everything and losing the positition in a large file. > > Best, -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
[O] can't export default koma letter
Hi,
I installed the get-stable version in ~/0work/org-mode and did the make on
it (see my previous email).
I then added
(push "~/0work/org-mode/lisp" load-path)
(push "~/0work/org-mode/etc" load-path)
(push "~/0work/org-mode/contrib" load-path)
(require 'org)
(eval-after-load 'ox '(require 'ox-koma-letter))
(eval-after-load 'ox-koma-letter
'(progn
(add-to-list 'org-latex-classes
'("my-letter"
"\\documentclass\{scrlttr2\}
\\usepackage[english]{babel}
\\setkomavar{frombank}{(1234)\\,567\\,890}
\[DEFAULT-PACKAGES]
\[PACKAGES]
\[EXTRA]"))
(setq org-koma-letter-default-class "my-letter")))
to my .emacs.
Now when I load up the attached koma example letter and try and export it
(C-c C-e k o) I get the following stack trace:
Debugger entered--Lisp error: (wrong-type-argument listp #("Romeo" 0 5
(:parent (#1
org-element-set-contents(#("Romeo" 0 5 (:parent (#0
apply(org-element-set-contents #("Romeo" 0 5 (:parent (#0))) nil)
#[(s) " \306\307\310 # \311\312 \211 :\204 \313\202\" @9\203! AA\202\"
)\"\210\314\315\n \211 :\2043\313\202@ @9\203? AA\202@ )#\210 \316\211\n
;\203V\317\320\f #\202\\\321 A@\f\"* \211 ;\203n\322 \313\f
$\202z A\323 A@\f
#\240\210 +\210\nA A@\240\210\n @\240*\207" [s new old element property
value replace-regexp-in-string "\n" " " mapc #[(blob) " \305 \211 ;\203
\306\f\307 \n$\202 \fA\310\fA@ \n#\240\210\f+\207" [blob old value property
element :parent org-add-props nil plist-put] 6] nil apply
org-element-set-contents :parent get-text-property 0 plist-get
org-add-props plist-put] 6](#("Romeo" 0 5 (:parent (#0
#[(--data) " \211 :\204 ;\205 \306\202 @9\205 @) ?\206\337 \203, \307
\310\">\206\337 \n\2047\311\f \"\202\337 \n\312=\203\\\311\f \211
:\204J\313\202W @9\203V AA\202W )\"\202\337 \n
>\203\202 !\211 \203\201 \203z\314\315 \"\210\202\201 B ) \316=\203\312
;\204\312\n \236A\313 \211 \203\311 @ \f ;\203\266\317\320 #\202\275\307 A@
\"*!\210 A\211 \204\234* \203\202 \316=\203\202 \n >\203\202 \313 \211
\203\201 @\211 @ A ;\203 \317\320 #\202 \307 A@ \"* ! \" !\203w \"
#\235\203_ \" $\235\203P \321 !!\313 %\211 \203L @ %\f %A!\210\f %@!\210
A\211 \2042 *\202w \f !A!\210\f !@!\210\202w \" $\235\203r \311\f\321
!!\"\210\202w \f !!\210* A\211 \204\350*\n &>\206\337 \211 :\204\224
\313\202\241 @9\203\240 AA\202\241 )?\206\337 \322=\203\265 \n '>?\206\337
\323=\203\303 \n (>\206\337 \311\f \211 :\204\320 \313\202\335
@9\203\334 AA\202\335
)\")\207" [--data element --type info --walk-tree types plain-text
plist-get :ignore-list mapc org-data nil throw --map-first-match objects
get-text-property 0 reverse greater-elements elements fun result
first-match --acc --category org-element-secondary-value-alist p
--dolist-tail-- property with-affiliated org-element-all-elements
org-element--parsed-properties-alist kwd-pair value kwd
org-element-dual-keywords org-element-multiple-keywords line no-recursion
org-element-greater-elements org-element-all-objects] 6](#("Romeo" 0 5
(:parent (#0
mapc(#[(--data) " \211 :\204 ;\205 \306\202 @9\205 @) ?\206\337 \203,
\307 \310\">\206\337 \n\2047\311\f \"\202\337 \n\312=\203\\\311\f \211
:\204J\313\202W @9\203V AA\202W )\"\202\337 \n
>\203\202 !\211 \203\201 \203z\314\315 \"\210\202\201 B ) \316=\203\312
;\204\312\n \236A\313 \211 \203\311 @ \f ;\203\266\317\320 #\202\275\307 A@
\"*!\210 A\211 \204\234* \203\202 \316=\203\202 \n >\203\202 \313 \211
\203\201 @\211 @ A ;\203 \317\320 #\202 \307 A@ \"* ! \" !\203w \"
#\235\203_ \" $\235\203P \321 !!\313 %\211 \203L @ %\f %A!\210\f %@!\210
A\211 \2042 *\202w \f !A!\210\f !@!\210\202w \" $\235\203r \311\f\321
!!\"\210\202w \f !!\210* A\211 \204\350*\n &>\206\337 \211 :\204\224
\313\202\241 @9\203\240 AA\202\241 )?\206\337 \322=\203\265 \n '>?\206\337
\323=\203\303 \n (>\206\337 \311\f \211 :\204\320 \313\202\335
@9\203\334 AA\202\335
)\")\207" [--data element --type info --walk-tree types plain-text
plist-get :ignore-list mapc org-data nil throw --map-first-match objects
get-text-property 0 reverse greater-elements elements fun result
first-match --acc --category org-element-secondary-value-alist p
--dolist-tail-- property with-affiliated org-element-all-elements
org-element--parsed-properties-alist kwd-pair value kwd
org-element-dual-keywords org-element-multiple-keywords line no-recursion
org-element-greater-elements org-element-all-objects] 6] (#("Romeo" 0 5
(:parent #0
#[(--data) " \211 :\204 ;\205 \306\202 @9\205 @) ?\206\337 \203, \307
\310\">\206\337 \n\2047\311\f \"\202\337 \n\312=\203\\\311\f \211
:\204J\313\202W @9\203V AA\202W )\"\202\337 \n
>\203\202 !\211 \203\201 \203z\314\315 \"\210\202\201 B ) \316=\203\312
;\204\312\n \236A\313 \211 \203\311 @ \f ;\203\266\317\320 #\202\275\307 A@
\"*!\210 A\211 \204\234* \203\202 \316=\203\202 \n >\203\202 \313 \211
\203\201 @\211 @ A ;\203 \317\320 #\202 \307 A@ \"* ! \" !\203w \"
#\235\203_ \" $\235\203P \321 !!\313 %\211 \203L @ %\f %A!\210\f %@!\210
A\211
[O] Can't store link in mu4e
I pulled the latest org from git a few days ago. Now I can no longer store links to email messages in mu4e with "C-c l". The message I get is No method for storing a link from this buffer Nothing else has changed, and I am still able to pull up email message by clicking on (old) links in org files, and org-capture of email messages still works with "C-c c". I'm running mu/mu4e version 0.9.17 from github and a snapshot of GNU Emacs 25 GNU Emacs 25.1.50.2 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 2016-08-23 Any ideas? I really depend on this functionality.
Re: [O] Can't store link in mu4e
Hello, Brett Presnell writes: > I pulled the latest org from git a few days ago. Now I can no longer > store links to email messages in mu4e with "C-c l". The message I get > is > > No method for storing a link from this buffer I had the same problem with wanderlust last week. But the next pull a couple of days ago fixed that for me. VG hmw
[O] Bug? Highlighting inconsistent with export
Hi all, In the following snippets, I have marked which bits are syntax-highlighted as code, and which bits are exported as code. Some “=code=” [fn:: ~more~ ~of it~]. ~even more code~— ~this~ —. Highlighted?NoYesNo NoNo Exported? NoYesYes NoNo Note the inconsistency in the footnote case. ~this~ isn't highlighted because it's surrounded by non-breaking space. ~of it~ isn't highlighted because of the ‘]’, but on export it does get rendered as code. Some suggestions: Paired delimiters and quotes, such as “” ‘’ <> [], could be allowed around code (by changing the default for ‘org-emphasis-regexp-components’). Spaces (including zero-width spaces) could also be allowed: this would provide a universal mechanism for ensuring that a bit of code is highlighted. For example, “There are many ~let~s in this code” wouldn't work, but “There are many ~let~s in this code” would work fine. Cheers, Clément. signature.asc Description: OpenPGP digital signature
Re: [O] DONE items skipped in org-map-entries
Hi Nicolas On Sun, Aug 28, 2016, at 15:15, Nicolas Goaziou wrote: > I'm not able to reproduce the issue. I tried with the following document > > ** DONE Foo > *** Bar > > with point anywhere on the first line, `org-count' displays "entries 2". Thank you; your reply led me to inspect my emacsrc more closely. The following customization caused the problem: (setq org-agenda-skip-function-global '(org-agenda-skip-entry-if 'todo 'done)) I didn't realize `org-map-entries` was tied to the agenda. Best regards Stéfan
Re: [O] Proposal and RFC for improving ob-python
hi. i recently got fed up with ob-python.el behavior w.r.t. :session handling (startup issues; blank lines [really, a python problem, imho, but a workaround maybe could work], and value scraping), looked, and saw this discussion from last December, but nothing since then. has there been any progress, either by Ondřej or anyone else? if my frustration level remains high enough, i might try to see if i can do anything. cheers, Greg Minshall
Re: [O] Emacs movement keys
> On 29-Aug-2016, at 6:55 pm, John Kitchin wrote: > >> You know you're an Emacs user when... > > You select some text in MS Word and Type C-w to cut it... and are very > unhappy when Word closes... Story of emacs users on OS X... Vikas
