Re: [O] 63 failures for org-test-run-all-tests in an Emacs GUI
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Nicolas Goaziou wrote: Sebastien Vauban writes: Did I misunderstand the change of last year (Dec '13) or should `sh' language be abandoned in favor of `shell'? I think you're right. IIUC, then, those blocks should be updated: ... And those inline calls as well: ... I am willing to make the patch. Great. Please do. Here it is. Thanks. Unfortunately, I'm still unable to apply your patch. Before using git format-patch, please ensure that your patch is the only one on top of HEAD, and send it again. If you already did, maybe someone else with write access to the repo will be able to sort it out. Regards,
Re: [O] [PATCH] ox-html.el: Add exporting of priority
Hello, Zane D. Purvis zane.pur...@gmail.com writes: * list/ox-html.el (org-html--priority): New function. (org-html-format-headline-default-function): Call `org-html--priority'. (org-html-style-default): Add `.priority'. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] doc patch: move footnote in external links
Sorry for the delay in answering …
On 2014-12-20 23:15, Nicolas Goaziou m...@nicolasgoaziou.fr writes:
-file:projects.org::*task title@r{heading search in Org file}
+file:projects.org::*task title@r{heading search in Org
file}@footnote{
+Headline searches always match the exact headline. If the headline is not
^^^
two spaces
It looks good.
Here is an updated patch. I can push it or not, depending on the issue
below.
From 7fa07604c85a6a5dd06a198232ae65c4f5c0272f Mon Sep 17 00:00:00 2001
From: Alan Schmitt alan.schm...@polytechnique.org
Date: Fri, 12 Dec 2014 08:26:05 +0100
Subject: [PATCH] Function `org-link-search' does exact headline search
* lisp/org.el (org-link-search): Change headline search such that it
always does an exact search.
* doc/org.texi (External links): Cleanup footnote about the
`org-link-search-must-match-exact-headline' option for text searches
and add a footnote about the effect of the same option for heading
searches.
---
doc/org.texi | 7 +--
lisp/org.el | 27 +++
2 files changed, 12 insertions(+), 22 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 54b6fe9..a179250 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -3561,10 +3561,13 @@ file:projects.org::some words @r{text search in Org file}@footnote{
The actual behavior of the search will depend on the value of
the option @code{org-link-search-must-match-exact-headline}. If its value
is @code{nil}, then a fuzzy text search will be done. If it is t, then only the
-exact headline will be matched. If the value is @code{'query-to-create},
+exact headline will be matched. If the value is @code{query-to-create},
then an exact headline will be searched; if it is not found, then the user
will be queried to create it.}
-file:projects.org::*task title@r{heading search in Org file}
+file:projects.org::*task title@r{heading search in Org file}@footnote{
+Headline searches always match the exact headline. If the headline is not
+found and the value of the option @code{org-link-search-must-match-exact-headline}
+is @code{query-to-create}, then the user will be queried to create it.}
file+sys:/path/to/file@r{open via OS, like double-click}
file+emacs:/path/to/file @r{force opening by Emacs}
docview:papers/last.pdf::NNN @r{open in doc-view mode at page}
diff --git a/lisp/org.el b/lisp/org.el
index e8e3356..4ed1f17 100755
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -11021,8 +11021,7 @@ visibility around point, thus ignoring
org-emphasis-alist)
\\|) \\)))
(pos (point))
- (pre nil) (post nil)
- words re0 re1 re2 re3 re4_ re4 re5 re2a re2a_ reall)
+ words re0 re2 re4_ re4 re5 re2a re2a_ reall)
(cond
;; First check if there are any special search functions
((run-hook-with-args-until-success 'org-execute-file-search-functions s))
@@ -11076,8 +11075,9 @@ visibility around point, thus ignoring
((derived-mode-p 'org-mode)
(org-occur (match-string 1 s)))
(t (org-do-occur (match-string 1 s)
- ((and (derived-mode-p 'org-mode) org-link-search-must-match-exact-headline)
- (and (equal (string-to-char s) ?*) (setq s (substring s 1)))
+ ((and (derived-mode-p 'org-mode)
+ (or (and (equal (string-to-char s) ?*) (setq s (substring s 1)))
+ org-link-search-must-match-exact-headline))
(goto-char (point-min))
(cond
((let (case-fold-search)
@@ -11099,11 +11099,6 @@ visibility around point, thus ignoring
(error No match
(t
;; A normal search string
- (when (equal (string-to-char s) ?*)
- ;; Anchor on headlines, post may include tags.
- (setq pre ^\\*+[ \t]+\\(?:\\sw+\\)?[ \t]*
- post (org-re [ \t]*\\(?:[ \t]+:[[:alnum:]_@#%:+]:[ \t]*\\)?$)
- s (substring s 1)))
(remove-text-properties
0 (length s)
'(face nil mouse-face nil keymap nil fontified nil) s)
@@ -11120,15 +5,9 @@ visibility around point, thus ignoring
[^a-zA-Z_\r\n]+) \\)[^a-zA-Z_])
re4 (concat [^a-zA-Z_] re4_)
- re1 (concat pre re2 post)
- re3 (concat pre (if pre re4_ re4) post)
- re5 (concat pre .* re4)
- re2 (concat pre re2)
- re2a (concat pre (if pre re2a_ re2a))
- re4 (concat pre (if pre re4_ re4))
- reall (concat \\( re0 \\)\\|\\( re1 \\)\\|\\( re2
- \\)\\|\\( re3 \\)\\|\\( re4 \\)\\|\\(
- re5 \\)))
+ re5 (concat .* re4)
+ reall (concat \\( re0 \\)\\|\\( re2 \\)\\|\\( re4
+ \\)\\|\\( re5 \\)))
(cond
((eq type 'org-occur) (org-occur reall))
((eq type 'occur) (org-do-occur (downcase reall) 'cleanup))
@@ -11136,10 +11125,8 @@ visibility around point, thus ignoring
(setq type 'fuzzy)
(if (or (and (org-search-not-self 1 re0 nil t)
(setq type 'dedicated))
-
Re: [O] Lentic.0.6 and org mode
On 2015-01-09 19:18, phillip.l...@newcastle.ac.uk (Phillip Lord) writes: I've used a similar configuration #+begin_src emacs-lisp (add-hook 'emacs-lisp-mode-hook (lambda () (setq lentic-init 'lentic-orgel-org-init))) #+end_src Personally, I wouldn't do that! At the moment, my transformation doesn't work nicely for all el files. At a minimum, you need code markers at the before the first line of lisp and the after the last. Otherwise, all the code gets treated by org as text; if you run, say, fill-paragraph in the org-mode lentic view then it will do bad things when all the code gets refilled. What are those markers? The #+begin_src one? Would you recommend using file-local variables for lentic files? I gave it a try with this file: lentic_test.el Description: application/emacs-lisp and it work well, with the exception of the file local variables that remain as text. but it's not as nice as in the demo. For instance, the following: #+begin_src emacs-lisp ;;; Code: ;; ** Startup ;; #+begin_src emacs-lisp ;; Turn off mouse interface early in startup to avoid momentary display (if (fboundp 'tool-bar-mode) (tool-bar-mode -1)) (if (fboundp 'scroll-bar-mode) (scroll-bar-mode -1)) #+end_src becomes #+begin_src org * Code ;; ** Startup ;; #+begin_src emacs-lisp ;; Turn off mouse interface early in startup to avoid momentary display (if (fboundp 'tool-bar-mode) (tool-bar-mode -1)) (if (fboundp 'scroll-bar-mode) (scroll-bar-mode -1)) #+end_src Why the Startup is not promoted at the org level? If your example is complete, I think it's because your code markers are unbalanced. Look in the *lentic-log* buffer and you should see lots of delimiters do not match. Put a ;; #+end_src in place and it should fix itself. This was not a full example, so there was the end marker. But as there is a lot of code below it as well (without markers), this may be the issue. The small example above works well. This should probably be smoothed over in the user interface. I could tell the user when the lentic buffer is created. You've also uncovered a bug -- when the delimiters do not match, it's should be doing the safest transformation of all which is a direct copy; so the * Code line should have been left alone also. By the way, what is the correct way of exiting lentic mode? For the moment I kill the buffer and the window, but it would be nice to have a function that exits lentic. Thanks, Alan -- OpenPGP Key ID : 040D0A3B4ED2E5C7 signature.asc Description: PGP signature
[O] 12.9.11.4 Customizing tables in ODT export -- Error in manual?
Hi there, in the manual, section 12.9.11.4 Customizing tables in ODT export the table style tag has superfluous quotes: #+ATTR_ODT: :style TableWithHeaderRowAndColumn This does not work. I guess it should be corrected to #+ATTR_ODT: :style TableWithHeaderRowAndColumn - thomas
Re: [O] 12.9.11.4 Customizing tables in ODT export -- Error in manual?
Hi Thomas, thomas tho...@friendlyvillagers.com writes: in the manual, section 12.9.11.4 Customizing tables in ODT export the table style tag has superfluous quotes: #+ATTR_ODT: :style TableWithHeaderRowAndColumn This does not work. I guess it should be corrected to #+ATTR_ODT: :style TableWithHeaderRowAndColumn Fixed. Thanks for reporting! BTW: The former syntax was changed quite a while back. Thanks, Rasmus -- Dung makes an excellent fertilizer
[O] bug: isearch hides text that should be shown, ignoring all show variables
a similar bug to bug: isearch puts ellipses at top of window [which has an ecm]: * aa * a text *** b text *** c text * d and isearch for text sometimes produces the output below at top of window: ... * a text ... * d and sometimes this: ... * a text *** b * d both are not what i want. to me, nothing should ever be hidden in org unless it can be hidden using arrow keys and tab. i don't have an ecm. samuel
