Re: [BUG] Org parser error: invalid search bound (wrong side of point) [9.7.7 (9.7.7-1ee080 @ /home/talmage/.emacs.d/elpa/org-9.7.7/)]
On Sunday, August 18, 2024 3:34:59 AM EDT Ihor Radchenko wrote: > David Talmage writes: > >> Are you seeing this problem frequently? > > > > Yesterday, I saw it every time I loaded Planning.org. Today, I loaded the > > file and Emacs didn't complain. I'll send more info when I have it. At > > the moment, I'm inclined to believe that this is one of my Linux Surface > > Pro tablet's many quirks. > > It has been a month since the last message in this thread. > David, may I know if you keep seeing the problem? Thank you for asking, Ihor. The problem went away. I don't know why.
Re: [BUG] Org parser error: invalid search bound (wrong side of point) [9.7.7 (9.7.7-1ee080 @ /home/talmage/.emacs.d/elpa/org-9.7.7/)]
On Thursday, July 18, 2024 1:57:50 AM CDT Ihor Radchenko wrote: > David Talmage writes: > > What I did: I visited Planning.org, a big Org Mode file I use to plan an > > extended motorcycle trip. > > > > What I expected: Emacs would load Planning.org, handing it off to Org > > Mode to Do The Right Thing, as it usually does. > > > > What occurred: Emacs complained of a parsing error. > > Thanks for reporting! > Are you seeing this problem frequently? Yesterday, I saw it every time I loaded Planning.org. Today, I loaded the file and Emacs didn't complain. I'll send more info when I have it. At the moment, I'm inclined to believe that this is one of my Linux Surface Pro tablet's many quirks.
[BUG] Org parser error: invalid search bound (wrong side of point) [9.7.7 (9.7.7-1ee080 @ /home/talmage/.emacs.d/elpa/org-9.7.7/)]
What I did: I visited Planning.org, a big Org Mode file I use to plan an
extended motorcycle trip.
What I expected: Emacs would load Planning.org, handing it off to Org
Mode to Do The Right Thing, as it usually does.
What occurred: Emacs complained of a parsing error.
Emacs : GNU Emacs 29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41,
cairo version 1.18.0)
of 2024-04-01, modified by Debian
Package: Org mode version 9.7.7 (9.7.7-1ee080 @ /home/talmage/.emacs.d/elpa/
org-9.7.7/)
current state:
==
(setq
org-link-elisp-confirm-function 'yes-or-no-p
org-bibtex-headline-format-function 'org-bibtex-headline-format-default
org-babel-after-execute-hook '(org-redisplay-inline-images)
org-agenda-files '("~/Documents/Travel/FourCornersByMoto-2024/Planning.org")
org-persist-after-read-hook '(org-element--cache-persist-after-read)
org-export-before-parsing-hook '(org-attach-expand-links)
org-cycle-tab-first-hook '(org-babel-hide-result-toggle-maybe org-babel-
header-arg-expand)
org-archive-hook '(org-attach-archive-delete-maybe)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-show-empty-lines
org-cycle-optimize-window-after-
visibility-change org-cycle-display-inline-images)
org-persist-before-read-hook '(org-element--cache-persist-before-read)
org-yank-image-file-name-function 'org-yank-image-autogen-filename
org-mode-hook '(#[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-
hook org-fold-show-all append local] 5]
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-
hook org-babel-show-result-all append local] 5]
org-babel-result-hide-spec org-
babel-hide-all-hashes
#[0 "\301\211\207" [imenu-create-
index-function org-imenu-get-tree] 2] turn-on-auto-fill)
org-confirm-shell-link-function 'yes-or-no-p
outline-isearch-open-invisible-function 'outline-isearch-open-invisible
org-sort-function 'string-collate-lessp
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-
edit-buffer)
org-confirm-elisp-link-function 'yes-or-no-p
org--warnings '("org-element--cache: Org parser error in Planning.org::
107349. Resetting.\n The error was: (error \"Invalid search bound (wrong side
of point)\")\n Backtrace:\nnil\n Please report this to Org mode mailing list
(M-x org-submit-bug-report).")
org-speed-command-hook '(org-speed-command-activate org-babel-speed-command-
activate)
org-fold-core-isearch-open-function 'org-fold--isearch-reveal
org-persist-before-write-hook '(org-element--cache-persist-before-write)
org-tab-first-hook '(org-babel-hide-result-toggle-maybe org-babel-header-arg-
expand)
org-link-shell-confirm-function 'yes-or-no-p
org-babel-pre-tangle-hook '(save-buffer)
org-agenda-loop-over-headlines-in-active-region nil
org-occur-hook '(org-first-headline-recenter)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-link-parameters '(("attachment" :follow org-attach-follow :complete org-
attach-complete-link)
("id" :follow org-
id-open :store org-id-store-link-maybe)
("eww" :follow org-
eww-open :store org-eww-store-link)
("rmail" :follow
org-rmail-open :store org-rmail-store-link)
("mhe" :follow org-
mhe-open :store org-mhe-store-link)
("irc" :follow org-
irc-visit :store org-irc-store-link :export org-irc-export)
("info" :follow org-
info-open :export org-info-export :store org-info-store-link
:insert-
description org-info-description-as-command)
("gnus" :follow org-
gnus-open :store org-gnus-store-link)
("docview" :follow
org-docview-open :export org-docview-export :store org-docview-store-link)
("bibtex" :follow
org-bibtex-open :store org-bibtex-store-link)
("bbdb" :follow org-
bbdb-open :export org-bbdb-export :complete org-bbdb-complete-link
:store org-
bbdb-store-link)
("w3m" :store org-
w3m-store-link)
("doi" :follow org-
link-doi-open :export org-link-doi-export) ("file+sys") ("file+emacs")
("shell" :follow
org-link--open-shell)
("news" :follow
#[514
"\301\300\302Q\"\207
Re: [O] Help checking orgcard.pdf
On Thu, Feb 9, 2017 at 1:02 PM, Kyle Meyer wrote:
> Kyle Meyer writes:
>
> > David Talmage writes:
>
> [...]
>
> >> There is a formatting bug in orgcard.tex. The US letter version,
> >> orgcard_letter.pdf, does not fit on the front and back of a single page
> as
> >> orgcard.pdf does.
> >
> > Thanks for catching that. It seems to be the extra line
> >
> > \metax{move the line at point up/down}{M-S-UP/DOWN}
> >
> > added in 4340cc78. I'll play around with it a bit to see if I can get
> > things to fit. At the worst, I'll remove that line.
>
> Should be fixed with fd565d6e6. There was a stale line in the
> ...
I confirm that it is fixed.
Thanks!
Re: [O] Insert git hash into exported document
On Fri, Dec 23, 2016 at 3:13 PM, Daniele Pizzolli wrote:
>
> David Talmage writes:
>
> > I'd like to insert the git hash of HEAD in the org-mode documents that I
> > export. Is there an easy way? I'm exporting to LaTeX.
>
> ...
#+NAME: hash-from-lisp
> #+BEGIN_SRC emacs-lisp
> (shell-command-to-string "git rev-parse HEAD" )
> #+END_SRC
>
> #+RESULTS: hash-from-lisp
> : 099b6ceee7264832b8e13f1156974b8017e6e4bb
>
> You can hide the result using proper headers or the noexport tag and
> then print the result in a verbose way:
>
> The latest commit hash is src_emacs-lisp[:var i=hash-from-lisp]{(format
> "%s" i)}
>
>
Thanks! That does what I want. Alas, it has a side effect. When I put
all that in my document, I get the hash I desire but I also get this Emacs
LISP code in my document:
\begin{verbatim}
(shell-command-to-string "git rev-parse HEAD" )
\end{verbatim}
I added :exports results to the BEGIN_SRC block to remove the code.
...
[O] Insert git hash into exported document
I'd like to insert the git hash of HEAD in the org-mode documents that I export. Is there an easy way? I'm exporting to LaTeX. I looked for it on worg. The mailing list on gmane.org is still off-line, alas.
Re: [O] transcluding some org-elements in multiple places
On Fri, Dec 9, 2016 at 11:28 AM, Eric S Fraga wrote: > On Friday, 9 Dec 2016 at 15:29, John Kitchin wrote: > > Hi all, > > > > I have an idea for how I could transclude "copies" or links to > > [...] > > > Any thoughts? Do you see any potential issues? > > Potentially very interesting and useful idea. Some thoughts/issues: > > I'm interested in this, too. In my lab notebook org file, I have a section that should be put into its own file and either linked or transcluded in several places. Transclusion would be better because I could see the text without following a link. It suits my lazy nature. ;-) > ... > > - what about more than level of indirection: link to a trancluded > headline which transcludes to another etc. What is shown? Is there a > performance hit? > > It seems to me that transclusion should be transitive. A transcluded org file should be able to transclude other org files. It should be transclusion all the way down. It also seems to me that org-mode transclusion must detect cycles so that it does not infinitely transclude documents. - what happens if the destination moves or gets deleted? the link to > it, which looked like something "complete" is now meaningless. This > could be quite confusing. This is probably the most serious issue. > How does org-mode handle broken links now? That's probably the right way to handle broken transclusion. > - the table aspect is almost a "view" on a database which is really > appealing but would benefit from a fully defined syntax a la sql? > Would table formulas work as expected from the view of the contents? > > Why wouldn't table formulas work? Transclusion is/could be/should be just another way to put org-mode formatted text into an org-mode buffer. ... > > - could we have "read-only" views? I may not want the original touched. > Perhaps that would be property of the transcluded document. > - how does an export work? On the view or the actual contents? > > Export works on the view.
Re: [O] Make wide tables more readable
On Thu, Dec 1, 2016 at 3:17 PM, David Talmage wrote: > ... > (fill-paragraph). I've already tried org-table-wrap-region and couldn't > figure it out. > I figured out org-table-wrap-region. Most of the time it works as expected. Sometimes it puts text cells below the one I want. I ended up manually justifying my cells in a few cases. Thank you all for the suggestions.
[O] Make wide tables more readable
I'm looking for ways to make a wide table more readable. My motivation is from a table that is too wide to fit on my screen. I need to be able to see all of the contents of a cell. If it were just text, I'd use M-q (fill-paragraph). I've already tried org-table-wrap-region and couldn't figure it out.
Re: [O] Release 9.0 test failed: test-ob/indented-cached-org-bracket-link
On Sun, Nov 20, 2016 at 3:38 AM, Nicolas Goaziou wrote: > Hello, > > "Charles C. Berry" writes: > > > OTOH, (expand-file-name "test.txt") resolves double-slashes and seems > > like the right idiom in any case. > > Fixed. Thank you. > It worked for me, too! Thank you all!
[O] Release 9.0 test failed: test-ob/indented-cached-org-bracket-link
I built org 9.0 on my Mac today. 'make test' reported one failed test. I
don't know if it is important or not. Please advise me.
'make test' said:
1 unexpected results:
FAILED test-ob/indented-cached-org-bracket-link
make: *** [test] Error 1
I have bash 4.4 freshly installed from mac ports.
I have emacs 24.5.1.
Here is the backtrace:
Test test-ob/indented-cached-org-bracket-link backtrace:
(if (unwind-protect (setq value-1119 (let ((default-directory tempor
(let (form-description-1120) (if (unwind-protect (setq value-1119 (l
(let ((value-1119 (cl-gensym "ert-form-evaluation-aborted-"))) (let
(lambda nil (let ((value-1119 (cl-gensym "ert-form-evaluation-aborte
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test test-ob/indented-cached-org-bracket
ert-run-or-rerun-test([cl-struct-ert--stats "\\(org\\|ob\\)" [[cl-st
ert-run-tests("\\(org\\|ob\\)" #[385 "\306\307\"\203G\211\211G\310
ert-run-tests-batch("\\(org\\|ob\\)")
ert-run-tests-batch-and-exit("\\(org\\|ob\\)")
(let ((org-id-track-globally t) (org-test-selector (if org-test-sele
org-test-run-batch-tests("\\(org\\|ob\\)")
eval((org-test-run-batch-tests org-test-select-re))
command-line-1(("--eval" "(setq vc-handled-backends nil org-startup-
command-line()
normal-top-level()
Test test-ob/indented-cached-org-bracket-link condition:
(ert-test-failed
((should
(let
(...)
(org-test-with-temp-text "
* Test
#+BEGIN_SRC emacs-lisp :file test.txt :cache yes
(message \"test\")
#+END_SRC" ... ...)))
:form
(let
((default-directory temporary-file-directory))
(org-test-with-temp-text "
* Test
#+BEGIN_SRC emacs-lisp :file test.txt :cache yes
(message \"test\")
#+END_SRC"
(org-babel-execute-src-block)
(string= ... ...)))
:value nil))
FAILED 166/670 test-ob/indented-cached-org-bracket-link
Re: [O] Bug: org-mode interprets * as a headline in text between #+BEGIN_.. and #+END_...
On Fri, Oct 7, 2016 at 2:09 AM, Nicolas Goaziou wrote: > Hello, > > Nick Dokos writes: > > > Is the "* on column 0 is a headline" convention a consequence of the > > dependence on outline.el? Or is it just historical baggage? I cannot > > remember the grammar rules, but I'm wondering if the parser could be > > made to say "not a headline" in this situation, and if so, what the > > consequences might be (particularly, the bad consequences). > > ... > > This is inherent on how the syntax is defined, and how the parser is > implemented. As an outliner, the main syntactic element in an Org > document is the headline. Everything else has a lower priority. > Therefore, a block will not be parsed before a headline. > > ... That's interesting. Thanks for the explanation. What does the parser do with a drawer? How is that different from a block? It seems that one can put text that looks like a headline in a drawer and it won't be interpreted as a headline. Why couldn't blocks be parsed the same way?
[O] Bug: org-mode interprets * as a headline in text between #+BEGIN_.. and #+END_...
I often paste verbatim text into the lab notebook I keep with org-mode.
Org-mode always interprets any line that begins with an asterisk as a
headline, even when the line is surrounded by #+BEGIN_... and #+END_...
patterns. This breaks org-special-edit, making it complain, "No special
environment to edit here", unless I manually insert another character at
the beginning of every line in the block that begins with an asterisk.
The behavior surprised me. I found two ways to work around it. First, I
can edit the would-be verbatim text as described above. It will always look
like the original text in org-special-edit. That's marginally acceptable
because it alters my original text and makes me take one more step before I
can copy and paste it elsewhere. Second, I can put such text in a drawer.
I discovered that org-mode does not mis-interpret my text in a drawer.
Here is an example. It's markdown text. I use #+{BEGIN,END}_EXAMPLE but
this behavior occurs in all of the #+BEGIN_.. and #+END_... patterns.
#+BEGIN_EXAMPLE
This is the README.md for rfc-tools, a collection of programs for
processing IETF RFCs.
* fetch-rfcs-by-title.sh downloads into the current directory the RFCs
whose titles contain the string given on the command line. Uses an
rfc-index file in the current directory. Prefers the PDF version of
RFCs but will obtain the text version if the PDF is not available.
* fetch-sip-rfcs.sh downloads RFCs that contain "Session Initiation"
in their titles into the current directory.
* search-rfc-index.sh searches an rfc-index file in the current
directory for the string given on the command line. The string can
contain spaces.
* join-titles.awk turns the contents of an rfc-index file into a
series of long lines. Each line begins with the RFC number, then a
space, then the rest of the entry from the rfc-index.
#+END_EXAMPLE
