Re: [O] Org-capture fails in Org 9.05
Hello, Jay Iyer writes: > new Mac and encountered an error that prevents org-capture to complete the > refiling step. I have attached a backtrace here for your review. > Please let me know if this is an installation error of some kind and how I > can fix it. > > ps: highly satisfied Org-moder for 4+ years now, haven't touched any other > organizer all that time! > Debugger entered--Lisp error: (void-function org-inhibit-invisibility) This function doesn't exist in the Org code base. > (org-inhibit-invisibility) [...] > wicked/org-update-checkbox-count(nil) You might want to look into this extension. Regards, -- Nicolas Goaziou
[O] Org-capture fails in Org 9.05
Hi, I installed Emacs 25.1 (Org 9.05 is built in to this version for Mac) on a new Mac and encountered an error that prevents org-capture to complete the refiling step. I have attached a backtrace here for your review. Please let me know if this is an installation error of some kind and how I can fix it. Thanks, -jay ps: highly satisfied Org-moder for 4+ years now, haven't touched any other organizer all that time! Debugger entered--Lisp error: (void-function org-inhibit-invisibility) (org-inhibit-invisibility) (let* ((buffer-invisibility-spec (org-inhibit-invisibility)) (beg (condition-case nil (progn (outline-back-to-heading) (point)) (error (point-min (end (move-marker (make-marker) (progn (or (outline-get-next-sibling) (goto-char (point-max))) (point (re "\\(\\[[0-9]*%\\]\\)\\|\\(\\[[0-9]*/[0-9]*\\]\\)") (re-box "^[ ]*\\(*+\\|[-+*]\\|[0-9]+[.)]\\) +\\(\\[[- X]\\]\\)") b1 e1 f1 c-on c-off lim (cstat 0)) (if all (progn (goto-char (point-min)) (or (outline-get-next-sibling) (goto-char (point-max))) (setq beg (point) end (point-max (goto-char beg) (while (re-search-forward re end t) (setq cstat (1+ cstat) b1 (match-beginning 0) e1 (match-end 0) f1 (match-beginning 1) lim (cond ((org-on-heading-p) (or (outline-get-next-sibling) (goto-char (point-max))) (point)) ((org-at-item-p) (org-end-of-item) (point)) (t nil)) c-on 0 c-off 0) (goto-char e1) (if lim (progn (while (re-search-forward re-box lim t) (if (member (match-string 2) (quote ...)) (setq c-off (1+ c-off)) (setq c-on (1+ c-on (goto-char b1) (insert (if f1 (format "[%d%%]" (/ ... ...)) (format "[%d/%d]" c-on (+ c-on c-off (and (looking-at "\\[.*?\\]") (replace-match "") (if (interactive-p) (progn (message "Checkbox statistics updated %s (%d places)" (if all "in entire file" "in current outline entry") cstat (save-excursion (let* ((buffer-invisibility-spec (org-inhibit-invisibility)) (beg (condition-case nil (progn (outline-back-to-heading) (point)) (error (point-min (end (move-marker (make-marker) (progn (or (outline-get-next-sibling) (goto-char ...)) (point (re "\\(\\[[0-9]*%\\]\\)\\|\\(\\[[0-9]*/[0-9]*\\]\\)") (re-box "^[ ]*\\(*+\\|[-+*]\\|[0-9]+[.)]\\) +\\(\\[[- X]\\]\\)") b1 e1 f1 c-on c-off lim (cstat 0)) (if all (progn (goto-char (point-min)) (or (outline-get-next-sibling) (goto-char (point-max))) (setq beg (point) end (point-max (goto-char beg) (while (re-search-forward re end t) (setq cstat (1+ cstat) b1 (match-beginning 0) e1 (match-end 0) f1 (match-beginning 1) lim (cond ((org-on-heading-p) (or (outline-get-next-sibling) (goto-char ...)) (point)) ((org-at-item-p) (org-end-of-item) (point)) (t nil)) c-on 0 c-off 0) (goto-char e1) (if lim (progn (while (re-search-forward re-box lim t) (if (member ... ...) (setq c-off ...) (setq c-on ...))) (goto-char b1) (insert (if f1 (format "[%d%%]" ...) (format "[%d/%d]" c-on ...))) (and (looking-at "\\[.*?\\]") (replace-match "") (if (interactive-p) (progn (message "Checkbox statistics updated %s (%d places)" (if all "in entire file" "in current outline entry") cstat) wicked/org-update-checkbox-count(nil) ad-Advice-org-update-checkbox-count((closure (t) (&optional all) "Update the checkbox statistics in the current section.\n\nThis will find all statistic cookies like [57%] and [6/12] and\nupdate them with the current numbers.\n\nWith optional prefix argument ALL, do this for the whole buffer." (interactive "P") (save-excursion (save-restriction (widen) (let* ((cookie-re "\\(\\(\\[[0-9]*%\\]\\)\\|\\(\\[[0-9]*/[0-9]*\\]\\)\\)") (box-re "^[ ]*\\([-+*]\\|\\([0-9]+\\|[A-Za-z]\\)[.)]\\)[ ]+\\(?:\\[@\\(?:start:\\)?\\([0-9]+\\|[A-Za-z]\\)\\][ ]*\\)?\\(\\[[- X]\\]\\)") (recursivep (or ... ...)) (within-inlinetask (and ... ... ...)) (end (cond ... ... ...)) (count-boxes (function ...)) cookies-list cache) (cond (all (goto-char ...)) (within-inlinetask (org-back-to-heading t)) (t (progn ... ... ... ... ...))) (while (re-search-forward cookie-re end t) (let (...) (if ... ...))) (let ((--dolist-tail-- cookies-list)) (while --dolist-tail-- (let ... ... ... apply(ad-Advice-org-update-checkbox-count (closure (t) (&optional all) "Update the checkbox statistics in the current section.\n\nThis will find all statistic cookies like [57%] and [6/12] and\nupdate them with the current numbers.\n\nWith optional prefix argument ALL, do this for the whole buffer." (interactive "P") (save-excursion (save-restriction (widen) (let* ((cookie-re "\\(\\(\\[[0-9]*%\\]\\)\\|\\(\\[[0-9]*/[0-9]*\\]\\)\\)") (box-re "^[ ]*\\([-+*]\\|\\([0-9]+\\|[A-Za-z]\\)[.)]\\)[ ]+\\(?:\\[@\\(?:start:\\)?\\([0-9]+\\|[A-Za-z]\\)\\][ ]*\\)?\\(\\[[- X]\\]\\)") (recursivep (or ... ...)) (within-inlinetask (and ... ... ...)) (end (cond ... ... ...)) (count-boxes (function ...)) cookies-list cache) (cond (all (goto-char ...)) (within-inlinetask (org-back-to-heading t)) (t (progn ... ... ... ... ...))) (while (re
Re: [O] org-annotate/collaboration?
Uwe Brauer writes: >> Uwe Brauer writes: > >> I think collaborators who have even a tiny familiarity with >> technological tools make the whole process much, much easier. >> Unfortunately I'm working with technophobes, the sort of people who >> call the browser "the internet", so I have almost no wiggle room at >> all... > > One of the annoying thing in collaboration is to use email that is why a > server client model is more convenient. > > Hm, my collaborator is neither technical skilled but willing to use the > command line, and he writes in latex anyway which requires some > understanding your folks seem not to have. > > Another option you could use is LyX (and therefore latex of some sort). > LyX has a tracker of changes similar to the one provided by OpenOffice > and friends. It also supports some version control system (forgot the > details). > > But then again that might all be too technical, shrug I think I could easily convince people to use an online system, or one that works in Markdown (which would be nice). The killer is the history tracking: everyone's used to Track Changes, and it would take a real revolution to dislodge them from that. Even I, the supposedly technical one, screw up git regularly. E
Re: [O] Is `head-include-scripts' flag reachable from OPTIONS?
On 15 Feb 2017, 13:43:34 -0500 Nick Dokos wrote: > #+BIND: org-html-head-include-scripts nil > > perhaps? Ah, yes. This works much better than what I had before, which was to put the following lines at the bottom of my source file. #+BEGIN_COMMENT Local Variables: eval: (setq org-html-head-include-scripts nil) End: #+END_COMMENT I didn't even know abot `#+BIND'. Many thanks!
[O] No agenda view at work, need guidance
After upgrading to Org 9.0.5 elpa (as part of trying out elpa for the first time ever) I get the 'pick agenda option menu'. Pickin "a" or "t" all I get is a message: "Invalid function: org-with-silentmodifications" OS: Corporaate tweak of Ubuntu 14.04 Emacs 24.3.1 Before doing the Org upgrade I used the version that come bundled with Emacs (Org 7.something). With the old configuration Org mode worked fine when it came to agenda view and managing todo-lists. There were some minor issues such as missing ox-latex that prompted my upgrade. Doing an internet search for the error message I get a host of hits. So far this one is the only one that seems relevant: http://tonyballantyne.com/tech/elpa-org-mode-and-invalid-function-org-with-silent-modifications/ Am I on the right track if I try this? (I am at home now, otherwise I would have tried right away) TIA -- Martin Schöön http://hem.bredband.net/b262106/index.html
Re: [O] Is `head-include-scripts' flag reachable from OPTIONS?
r...@tamos.net writes: > When I export to html, it puts a javascript
Re: [O] Why is Org PDF LaTeX Output not readonly?
On Wednesday, 15 Feb 2017 at 16:07, Florian Lindner wrote: > The exported PDF opens in okular (xdg-open) and I'm perfectly happy with it. > I think we're talking about different > things. I mean the buffer that contains the output of the latex command and > potential error message, looking like: Oh, sorry, I misunderstood. Well, as Nick says, does it really matter as editing it won't affect anything? Funnily enough, I never see this buffer unless I go looking for it. Maybe there's an org setting that causes this buffer to be displayed or not? I cannot see one. -- : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8 signature.asc Description: PGP signature
[O] Is `head-include-scripts' flag reachable from OPTIONS?
When I export to html, it puts a javascript
Re: [O] basic spreadsheet question
Am Dienstag, 14. Februar 2017, 21:06:38 CET schrieb Jude DaShiell: > When currency is calculated, is it possible in org-mode to have a "$" > prefix on currency amounts? > > > -- Probably not. See here: https://emacs.stackexchange.com/questions/15076/how-to-add-dollar-amounts-in-org-mode -- Regards, Alexander
Re: [O] Why is Org PDF LaTeX Output not readonly?
Florian Lindner writes: > Am 15.02.2017 um 15:22 schrieb Eric S Fraga: > The exported PDF opens in okular (xdg-open) and I'm perfectly happy with it. > I think we're talking about different > things. I mean the buffer that contains the output of the latex command and > potential error message, looking like: > > Latexmk: This is Latexmk, John Collins, 5 Sep. 2016, version: 4.48. Why does it matter? -- Nick
Re: [O] Why is Org PDF LaTeX Output not readonly?
Am 15.02.2017 um 15:22 schrieb Eric S Fraga:
> On Wednesday, 15 Feb 2017 at 14:02, Florian Lindner wrote:
>> Hello,
>>
>> is there any reason why the output buffer of org mode exporting to
>> LaTeX is not read-only? Read-only is probably not the
>> right expression, what I mean is that e.g. q calls quit-window and
>> closes the window. This way it's done by Auctex.
>
> It is for me as the PDF is displayed in a docview window. I.e. if I
> export to "PDF and open" and then type 'q' in that buffer, the window is
> buried ('k' kills the window). What version of emacs are you using?
Hey,
I'm using
GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.7) of 2017-02-07
Org mode version 9.0.5 (9.0.5-elpa @ /home/florian/.emacs.d/elpa/org-20170210/)
The exported PDF opens in okular (xdg-open) and I'm perfectly happy with it. I
think we're talking about different
things. I mean the buffer that contains the output of the latex command and
potential error message, looking like:
Latexmk: This is Latexmk, John Collins, 5 Sep. 2016, version: 4.48.
Rule 'pdflatex': Rules & subrules not known to be previously run:
pdflatex
Rule 'pdflatex': The following rules & subrules became out-of-date:
'pdflatex'
Run number 1 of rule 'pdflatex'
Running 'pdflatex -recorder "./RBF.tex"'
Latexmk: applying rule 'pdflatex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Arch Linux)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./RBF.tex
LaTeX2e <2016/03/31> patch level 3
Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
(/usr/share/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/size11.clo))
[...]
Best,
Florian
Re: [O] Why is Org PDF LaTeX Output not readonly?
On Wednesday, 15 Feb 2017 at 14:02, Florian Lindner wrote:
> Hello,
>
> is there any reason why the output buffer of org mode exporting to
> LaTeX is not read-only? Read-only is probably not the
> right expression, what I mean is that e.g. q calls quit-window and
> closes the window. This way it's done by Auctex.
It is for me as the PDF is displayed in a docview window. I.e. if I
export to "PDF and open" and then type 'q' in that buffer, the window is
buried ('k' kills the window). What version of emacs are you using?
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
signature.asc
Description: PGP signature
[O] Why is Org PDF LaTeX Output not readonly?
Hello, is there any reason why the output buffer of org mode exporting to LaTeX is not read-only? Read-only is probably not the right expression, what I mean is that e.g. q calls quit-window and closes the window. This way it's done by Auctex. Thanks, Florian
