Re: image-file-name-regexp: Wrong type argument: characterp
Janek F writes: > I wanted to mark certain filenames as images and added this to my config.el: > > (add-to-list 'image-file-name-regexps "/preview/") > > But when I run `org-toggle-inline-images` now, I get the following error. > > image-file-name-regexp: Wrong type argument: characterp, "/preview/" This is likely because you are using the bleeding edge Emacs. Please update your Emacs to fix the issue, which is on Emacs side. See https://lists.gnu.org/archive/html/emacs-devel/2022-08/msg4.html Best, Ihor
Re: [PATCH] Re: [BUG] org-attach-id-ts-folder-format fails on customized IDs [9.6 (9.6-??-2e9999783)]
Just now had a closer look at your patch, and I don't like the hashing. My whole idea customizing ids is to make the file structure useful by itself, too. This is how I patched it for me: (defun xf/org-attach-id-folder-format (id) "Translate any ID into a folder-path." (format "%s/%s" (substring id 0 2) (if (> (seq-length id) 2) (substring id 2) id)) ) (setq org-attach-id-to-path-function-list '(xf/org-attach-id-folder-format)) --- Original Message --- Ihor Radchenko schrieb am Samstag, 23. Juli 2022 um 07:21: > Janek F xer...@pm.me writes: > > > When setting org-id-method to 'ts or 'org, > > org-attach seems to use org-attach-id-ts-folder-format > > to create its hierarchy. > > > > However I tend to customize IDs for important files by hand, > > causing any attempt to use org-attach on that file to fail > > if the ID is shorter than six characters: > > > > org-attach-id-ts-folder-format: Args out of range: "ftt", 0, 6 > > > > This method should be adjusted to handle non-ts-ids just as well, > > as org-id-method does not dictate the format of existing ids. > > > Thanks for reporting! > Tentative patch is attached. > > I have added some fallbacks for the default attach folder formatters, so > that they can work when the ID does not conform to specific format. > > This change is somewhat opinionated, so feel free to suggest alternative > solutions/fallback options. > > Best, > Ihor
image-file-name-regexp: Wrong type argument: characterp
Hello,
I wanted to mark certain filenames as images and added this to my config.el:
(add-to-list 'image-file-name-regexps "/preview/")
But when I run `org-toggle-inline-images` now, I get the following error.
image-file-name-regexp: Wrong type argument: characterp, "/preview/"
Even though it says:
```lisp
image-file-name-regexps is a variable defined in image-file.el.gz.
Value
("/preview/")
Documentation
List of regexps matching image-file filenames.
```And the variable is clearly a list.
As posted in
[https://emacs.stackexchange.com/questions/72902/image-file-name-regexp-wrong-type-argument-characterp](https://emacs.stackexchange.com/questions/72902/image-file-name-regexp-wrong-type-argument-characterp?noredirect=1#comment118105_72902)
Best,
Janek
Re: Exporting tables from python code block: Wrong type argument: markerp, nil
Mark Barton writes: > On Aug 2, 2022, at 6:58 AM, Darren Syzling wrote: > > If I execute the code in the editor the org-mode table appears in the > results. If I export to html or pdf I get the error: > org-babel-insert-result: Wrong type argument: markerp, nil. > > I also am experiencing this error. > Org mode version 9.5.4 (release_9.5.4-17-g6e991f @ > /Applications/Emacs.app/Contents/Resources/lisp/org/) > GNU Emacs 29.0.50 (build 1, x86_64-apple-darwin21.5.0, NS appkit-2113.50 > Version 12.4 (Build 21F79)) of 2022-08-01 > > In order to export the pdf, I evaluated the following to disable having the > export execute the src blocks and just manually > ran them to have the updated results inserted into the org file. > (setq org-export-use-babel nil) > > The last time I exported that document successfully was 2022-05-10. > Note that a bug was recently found in Emacs 29 relating to byte compilation which was generating this error. Apparently it also causes problems with backwards compatibility of *.elc files. Not sure if it has been fixed in Emacs master yet, but my recommendation would be to do a git pull for Emacs, followed by a make extraclean, ./autogent.sh, ./configure and make and then a rebuild of any additional packages you have installed.
Re: Adding target and custom id links doesn't ask for description
A few more details. My org-mode version 9.5.4 (9.5.4-ge0b05b). This is the link that org-insert-link inserts for <>: [[here][file:~/Desktop/Org/capturas.org::here]] This is the link that org-insert-link inserts for CUSTOM_ID = cusid: [[#cusid][file:~/Desktop/Org/capturas.org::#cusid]] Perhaps description and link are swapped? In both cases the full path is redundant since the link is pointing to the current file, but the verbosity is arguably less adequate for the description field. Best regards — Carlos
Adding target and custom id links doesn't ask for description
Hi all, When storing a <> or CUSTOM_ID link with org-store-link and then adding it with C-c C-l, org doesn’t ask for a description but automatically inserts an ugly description like: ~/Desktop/Org/captures.org::target or: ~/Desktop/Org/captures.org::#7EFBCEA1-0D17-45B9-A125-10FE581752F8 The entire path is inserted even when the target itself is simply “target”. But, more importantly, no chance to change the description is given to the user. This behavior is not observed when an ID link is stored, which seems pretty inconsistent since there is no clear difference wrt the CUSTOM_ID case. The inconvenience of this behavior and the inconsistent treatment of ID vs CUSTOM_ID makes me believe that this is not intended but a bug (perhaps a regression, but I’ve not been using org-mode for long enough to say). The source of this behavior is in org-store-link: ;; If store function actually set `:description' property, use ;; it, even if it is nil. Otherwise, fallback to link value. (setq desc (if (plist-member org-store-link-plist :description) (plist-get org-store-link-plist :description) link))) so that auto-desc is later assumed in org-insert-link, even then the store function has provided no description at all! Best regards — Carlos
Re: commit e22b4eb7 kills formatting & color
> Ihor Radchenko writes: > Colin Baxter writes: >> I disable popups so I always receive a buffer with: >> >> --8<---cut here---start->8--- >> The local variables list in test.org or .dir-locals.el contains >> values that may not be safe (*). > Thanks! > Can you try the attached patch? I've applied your patch and it seems to work me. As far as I can tell my org files and agenda now look and behave as normal. Thanks.
[PATCH] org-id: Fix ‘org-id-locations’ variable name in error message
Hi, While doing some stuff with org-mode, I noticed the error message "Could not read ‘org-id-values’ from ~/.emacs.d/whatever, setting it to nil". I quicly understood it’s related to org-id, but the only occurence I found for ‘org-id-values’ was in that exact error message. I wonder if this is not a little typo and the error message should speak of ‘ord-id-locations’ instead? This patch fix that problem. I’ve signed the GNU paper to make patch to GNU project if it matters. I can send a copy of it to anyone if needed. As this is my first contribution, I hope I do it well. Have a nice day, Étienne Signed-off-by: Étienne Deparis --- lisp/org-id.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org-id.el b/lisp/org-id.el index 13a831590..f54e7280a 100644 --- a/lisp/org-id.el +++ b/lisp/org-id.el @@ -595,7 +595,7 @@ If SILENT is non-nil, messages are suppressed." (setf (car item) (expand-file-name (car item) loc org-id-locations))) (error -(message "Could not read `org-id-values' from %s, setting it to nil" +(message "Could not read `org-id-locations' from %s, setting it to nil" org-id-locations-file (setq org-id-files (mapcar 'car org-id-locations)) (setq org-id-locations (org-id-alist-to-hash org-id-locations -- 2.37.1
Re: Exporting tables from python code block: Wrong type argument: markerp, nil
> On Aug 2, 2022, at 6:58 AM, Darren Syzling wrote: > > If I execute the code in the editor the org-mode table appears in the > results. If I export to html or pdf I get the error: org-babel-insert-result: > Wrong type argument: markerp, nil. I also am experiencing this error. Org mode version 9.5.4 (release_9.5.4-17-g6e991f @ /Applications/Emacs.app/Contents/Resources/lisp/org/) GNU Emacs 29.0.50 (build 1, x86_64-apple-darwin21.5.0, NS appkit-2113.50 Version 12.4 (Build 21F79)) of 2022-08-01 In order to export the pdf, I evaluated the following to disable having the export execute the src blocks and just manually ran them to have the updated results inserted into the org file. (setq org-export-use-babel nil) The last time I exported that document successfully was 2022-05-10. Mark
Re: [BUG] [9.6 (9.6-??-e9da29b @ /Users/bytedance/.emacs.d/.local/straight/build-28.1/org/)]
Cheng Zhao writes: > Remember to cover the basics, that is, what you expected to happen and > what in fact did happen. You don't know how to make a good report? See Could you please detail what happened? Best, Ihor
Exporting tables from python code block: Wrong type argument: markerp, nil
I'm not sure whether this is an issue with orgmode or my recent Emacs
build, I'm struggling to export orgmode tables from a python code block to
html/pdf.
Version info:
orgmode 9.5.4
GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, cairo
version 1.16.0) of 2022-07-29
Note my Emacs is a custom build with native compilation, json and GTK
support - which may be an issue - i.e. taken straight from the latest code
in github.
My simple test case would be something like:
#+begin_src python :results value raw :exports both
import pandas as pd
from tabulate import tabulate
df = pd.DataFrame({'A': [1, 2], 'B': [3, 4]})
return tabulate(df, headers=df.columns, tablefmt='orgtbl')
#+end_src
If I execute the code in the editor the org-mode table appears in the
results. If I export to html or pdf I get the
error: org-babel-insert-result: Wrong type argument: markerp, nil.
Even a simple example such as the following fails to export but will show
inline.
#+begin_src python :results table :exports both
return [['A', 1], ['B', 2]]
#+end_src
Stack trace on failure is below - hence why I was concerned with the custom
Emacs build:
jit-lock--run-functions(248 324)
jit-lock-fontify-now(248 #>)
org-font-lock-ensure(248 #>)
org-table-align()
org-table-next-field()
funcall-interactively(org-table-next-field)
#(org-table-next-field nil nil)
call-interactively@ido-cr+-record-current-command(# org-table-next-field nil nil)
apply(call-interactively@ido-cr+-record-current-command # (org-table-next-field nil nil))
call-interactively(org-table-next-field nil nil)
org-cycle()
org-babel-insert-result("|| A | B |\n|+-+-|\n| 0 |
1 |..." ("raw" "value" "replace") ("python" "import pandas as pd\nfrom
tabulate import tabulate\n..." ((:colname-names) (:rowname-names)
(:result-params "raw" "value" "replace") (:result-type . value) (:results .
"raw value replace") (:exports . "both") (:cache . "no") (:hlines . "no")
(:noweb . "no") (:session . "none") (:tangle . "no")) "" nil 11 "(ref:%s)")
nil "python")
org-babel-execute-src-block(nil ("python" "import pandas as pd\nfrom
tabulate import tabulate\n..." ((:colname-names) (:rowname-names)
(:result-params "replace" "value" "raw") (:result-type . value) (:results .
"replace value raw") (:exports . "both") (:tangle . "no") (:session .
"none") (:noweb . "no") (:hlines . "no") (:cache . "no")) "" nil 11
"(ref:%s)"))
org-babel-exp-results(("python" "import pandas as pd\nfrom tabulate
import tabulate\n..." ((:cache . "no") (:colname-names) (:exports . "both")
(:hlines . "no") (:noweb . "no") (:result-params "replace" "value" "raw")
(:result-type . value) (:results . "replace value raw") (:rowname-names)
(:session . "none") (:tangle . "no")) "" nil 11 "(ref:%s)") block nil
"8ef5c3d71f4f16777939d1b561458e5435a5e4a4")
org-babel-exp-do-export(("python" "import pandas as pd\nfrom tabulate
import tabulate\n..." ((:cache . "no") (:colname-names) (:exports . "both")
(:hlines . "no") (:noweb . "no") (:result-params "replace" "value" "raw")
(:result-type . value) (:results . "replace value raw") (:rowname-names)
(:session . "none") (:tangle . "no")) "" nil 11 "(ref:%s)") block
"8ef5c3d71f4f16777939d1b561458e5435a5e4a4")
org-babel-exp-src-block()
org-babel-exp-process-buffer()
org-export-as(html nil nil nil (:output-file "test-case.html"))
org-export-to-file(html "test-case.html" nil nil nil nil nil)
org-html-export-to-html(nil nil nil nil)
org-export-dispatch(nil)
funcall-interactively(org-export-dispatch nil)
#(org-export-dispatch nil nil)
call-interactively@ido-cr+-record-current-command(# org-export-dispatch nil nil)
apply(call-interactively@ido-cr+-record-current-command # (org-export-dispatch nil nil))
call-interactively(org-export-dispatch nil nil)
command-execute(org-export-dispatch)
Darren
Re: commit e22b4eb7 kills formatting & color
Colin Baxter writes:
> I disable popups so I always receive a buffer with:
>
> --8<---cut here---start->8---
> The local variables list in test.org
> or .dir-locals.el contains values that may not be safe (*).
Thanks!
Can you try the attached patch?
Best,
Ihor
>From 8348c62250d2ef92da92416ae13d91289b2abe01 Mon Sep 17 00:00:00 2001
Message-Id: <8348c62250d2ef92da92416ae13d91289b2abe01.1659448323.git.yanta...@gmail.com>
From: Ihor Radchenko
Date: Tue, 2 Aug 2022 21:50:20 +0800
Subject: [PATCH] org-mode: Prevent early fontification
* lisp/org.el (org-mode): Avoid triggering fontification when
`hack-local-variables' popup window is displayed. Font-lock settings
are not configured yet at this point.
Fixes https://orgmode.org/list/87r120kodw@yandex.com
---
lisp/org.el | 68 +
1 file changed, 37 insertions(+), 31 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index 214652364..f8977bba5 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -4708,37 +4708,43 @@ (define-derived-mode org-mode outline-mode "Org"
\\{org-mode-map}"
(setq-local org-mode-loading t)
- ;; Apply file-local and directory-local variables, so that Org
- ;; startup respects them. See
- ;; https://list.orgmode.org/587be554-906c-5370-2cf2-f08b14fa5...@gmail.com/T/#u
- (hack-local-variables 'ignore-mode-settings)
- (org-load-modules-maybe)
- (org-install-agenda-files-menu)
- (when (and org-link-descriptive
- (eq org-fold-core-style 'overlays))
-(add-to-invisibility-spec '(org-link)))
- (org-fold-initialize (or (and (stringp org-ellipsis) (not (equal "" org-ellipsis)) org-ellipsis)
-"..."))
- (make-local-variable 'org-link-descriptive)
- (when (eq org-fold-core-style 'overlays) (add-to-invisibility-spec '(org-hide-block . t)))
- (if org-link-descriptive
- (org-fold-core-set-folding-spec-property (car org-link--link-folding-spec) :visible nil)
-(org-fold-core-set-folding-spec-property (car org-link--link-folding-spec) :visible t))
- (setq-local outline-regexp org-outline-regexp)
- (setq-local outline-level 'org-outline-level)
- (when (and (stringp org-ellipsis) (not (equal "" org-ellipsis)))
-(unless org-display-table
- (setq org-display-table (make-display-table)))
-(set-display-table-slot
- org-display-table 4
- (vconcat (mapcar (lambda (c) (make-glyph-code c 'org-ellipsis))
- org-ellipsis)))
-(setq buffer-display-table org-display-table))
- (org-set-regexps-and-options)
- (org-set-font-lock-defaults)
- (when (and org-tag-faces (not org-tags-special-faces-re))
-;; tag faces set outside customize force initialization.
-(org-set-tag-faces 'org-tag-faces org-tag-faces))
+ ;; Disable `font-lock-mode' temporarily to delay fontification in case if
+ ;; `hack-local-variables' shows a popup window. Such a popup causes
+ ;; redisplay and triggers fontification too early.
+ (let ((org-font-lock-enabled-p font-lock-mode))
+(font-lock-mode -1)
+;; Apply file-local and directory-local variables, so that Org
+;; startup respects them. See
+;; https://list.orgmode.org/587be554-906c-5370-2cf2-f08b14fa5...@gmail.com/T/#u
+(hack-local-variables 'ignore-mode-settings)
+(org-load-modules-maybe)
+(org-install-agenda-files-menu)
+(when (and org-link-descriptive
+ (eq org-fold-core-style 'overlays))
+ (add-to-invisibility-spec '(org-link)))
+(org-fold-initialize (or (and (stringp org-ellipsis) (not (equal "" org-ellipsis)) org-ellipsis)
+ "..."))
+(make-local-variable 'org-link-descriptive)
+(when (eq org-fold-core-style 'overlays) (add-to-invisibility-spec '(org-hide-block . t)))
+(if org-link-descriptive
+(org-fold-core-set-folding-spec-property (car org-link--link-folding-spec) :visible nil)
+ (org-fold-core-set-folding-spec-property (car org-link--link-folding-spec) :visible t))
+(setq-local outline-regexp org-outline-regexp)
+(setq-local outline-level 'org-outline-level)
+(when (and (stringp org-ellipsis) (not (equal "" org-ellipsis)))
+ (unless org-display-table
+(setq org-display-table (make-display-table)))
+ (set-display-table-slot
+ org-display-table 4
+ (vconcat (mapcar (lambda (c) (make-glyph-code c 'org-ellipsis))
+ org-ellipsis)))
+ (setq buffer-display-table org-display-table))
+(org-set-regexps-and-options)
+(org-set-font-lock-defaults)
+(when (and org-tag-faces (not org-tags-special-faces-re))
+ ;; tag faces set outside customize force initialization.
+ (org-set-tag-faces 'org-tag-faces org-tag-faces))
+(font-lock-mode org-font-lock-enabled-p))
;; Calc embedded
(setq-local calc-embedded-open-mode "# ")
;; Modify a few syntax entries
--
2.35.1
Re: [BUG] org-forward-sentence does not recognize the end of sentences with footnotes [9.5.4 (N/A @ /gnu/store/zi4gr63h5k2w3y5srydk3k05bjrx9pi9-emacs-org-9.5.4/share/emacs/site-lisp/org-9.5.4/)]
Ihor Radchenko writes:
> "Dr. Arne Babenhauserheide" writes:
>
>> If you go to the first word in the following paragraph and press M-e
>> (org-forward-sentence), the point jumps to the end of the paragraph. But
>> it should jump to just after the footnote [fn:23].
>>
>> If I remove the footnote [fn:23], it correctly jumps to the end of the
>> first colon:
>>
>> Die Anzahl und Stärke der Werte ist durch eure
>> gewählte Machtstufe begrenzt:[fn:23] Ein starker
>> Wert@@latex:\index{Starker Wert}@@ kostet einen Punkt und ein
>> überragender Wert@@latex:\index{überragender Wert}@@ drei
>> Punkte.[fn:133] Starke Werte markiert ihr mit =+=, überragende Werte
>> mit =++=.
>
> But colon is not a sentence end. Or do I miss something?
I think I added colon there; in default setting this should jump to the
end of [fn:133]. If you have sentence with two spaces set, try adding a
space after [fn:133] — it is not recognized as end of a sentence:
Die Anzahl und Stärke der Werte ist durch eure
gewählte Machtstufe begrenzt:[fn:23] Ein starker
Wert@@latex:\index{Starker Wert}@@ kostet einen Punkt und ein
überragender Wert@@latex:\index{überragender Wert}@@ drei
Punkte.[fn:133] Starke Werte markiert ihr mit =+=, überragende Werte
mit =++=.
Wheras without the footnote it is:
Die Anzahl und Stärke der Werte ist durch eure
gewählte Machtstufe begrenzt:[fn:23] Ein starker
Wert@@latex:\index{Starker Wert}@@ kostet einen Punkt und ein
überragender Wert@@latex:\index{überragender Wert}@@ drei
Punkte. Starke Werte markiert ihr mit =+=, überragende Werte
mit =++=.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
signature.asc
Description: PGP signature
Re: commit e22b4eb7 kills formatting & color
> Ihor Radchenko writes: > Colin Baxter writes: >> No, I spoke too soon. That is not the answer. For me using "emacs >> -q", an opened org file will expand the folds using but >> there is still no synatx coloring. This is probably not relevant >> but my system is 32bit not 64. > Hmm. I was able to reproduce the issue using some slightly > non-standard settings. However, only when there is a popup window > asking about non-safe file-local variables. Does it also happen > for you after such a popup? Or do you have the settings marked > safe? I disable popups so I always receive a buffer with: --8<---cut here---start->8--- The local variables list in test.org or .dir-locals.el contains values that may not be safe (*). Do you want to apply it? You can type y -- to apply the local variables list. n -- to ignore the local variables list. ! -- to apply the local variables list, and permanently mark these values (*) as safe (in the future, they will be set automatically.) i -- to ignore the local variables list, and permanently mark these values (*) as ignored --8<---cut here---end--->8--- I then enter "y". It's a habit of mine never to use "!" even for files I use every day. I cannot remember ever entering "n" or "i". Best wishes,
Bug? org-id-find not finding some IDs
Hello, The documentation for org-id-extra-files suggests that org-id-find should search in Org files visited by Emacs: > When Org reparses files to remake the list of files and IDs it is > tracking, it will normally scan the agenda files, the archives > related to agenda files, ... and any Org file currently visited by > Emacs. But, I've found that's not true, or maybe I'm misunderstanding the doc. For a minimal example, put the following in test.org: > * Headline 1 > :PROPERTIES: > :ID: b1569c92-3872-4ab9-80eb-274c4950991e > :END: Then: 1. emacs -Q test.org 2. C-x b *scratch* 3. M-: (org-id-find "b1569c92-3872-4ab9-80eb-274c4950991e") Which returns nil. Also, "C-h v org-id-files" doesn't contain test.org. Or maybe the docstring for org-id-extra-files should be rewritten to say "the current buffer" instead of "any Org file currently visited"? Also, this seems to be the cause of this bug in org-caldav, which is how I ran into it: https://github.com/dengste/org-caldav/issues/230 Would there a recommended mitigation for this on org-caldav's side? I'm thinking it could call (org-id-update-id-locations org-caldav-files) early on, to make sure org-caldav-files ends up in org-id-files. Tested on following versions: GNU Emacs 28.1 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.6, Xaw3d scroll bars) of 2022-07-10 Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/) Org mode version 9.5.4 (release_9.5.4-702-g5a49cc @ /home/jack/dev/org-mode/lisp/)
Re: [BUG] org-forward-sentence does not recognize the end of sentences with footnotes [9.5.4 (N/A @ /gnu/store/zi4gr63h5k2w3y5srydk3k05bjrx9pi9-emacs-org-9.5.4/share/emacs/site-lisp/org-9.5.4/)]
"Dr. Arne Babenhauserheide" writes:
> If you go to the first word in the following paragraph and press M-e
> (org-forward-sentence), the point jumps to the end of the paragraph. But
> it should jump to just after the footnote [fn:23].
>
> If I remove the footnote [fn:23], it correctly jumps to the end of the
> first colon:
>
> Die Anzahl und Stärke der Werte ist durch eure
> gewählte Machtstufe begrenzt:[fn:23] Ein starker
> Wert@@latex:\index{Starker Wert}@@ kostet einen Punkt und ein
> überragender Wert@@latex:\index{überragender Wert}@@ drei
> Punkte.[fn:133] Starke Werte markiert ihr mit =+=, überragende Werte
> mit =++=.
But colon is not a sentence end. Or do I miss something?
sentence-end-base is a variable defined in paragraphs.el.
Value
"[.?!…‽][]\"'”’)}»›]*"
Best,
Ihor
[BUG] [9.6 (9.6-??-e9da29b @ /Users/bytedance/.emacs.d/.local/straight/build-28.1/org/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Emacs : GNU Emacs 28.1 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60
Version 10.14.6 (Build 18G95))
of 2022-05-12
Package: Org mode version 9.6 (9.6-??-e9da29b @
/Users/bytedance/.emacs.d/.local/straight/build-28.1/org/)
current state:
==
(setq
org-link-elisp-confirm-function nil
org-directory "~/org/"
org-after-refile-insert-hook '(save-buffer)
org-indirect-buffer-display 'current-window
org-crypt-key nil
org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn
ENTRY)"]
org-load-hook '(+org-init-org-directory-h +org-init-appearance-h
+org-init-agenda-h +org-init-attachments-h +org-init-babel-h
+org-init-babel-lazy-loader-h +org-init-capture-defaults-h
+org-init-capture-frame-h +org-init-custom-links-h
+org-init-export-h +org-init-habit-h +org-init-hacks-h
+org-init-keybinds-h +org-init-popup-rules-h +org-init-smartparens-h)
org-startup-folded nil
org-babel-after-execute-hook '(+org-redisplay-inline-images-in-babel-result-h)
org-link-abbrev-alist '(("doom-repo" .
"https://github.com/hlissner/doom-emacs/%s;) ("wolfram" .
"https://wolframalpha.com/input/?i=%s;)
("wikipedia" . "https://en.wikipedia.org/wiki/%s;)
("duckduckgo" . "https://duckduckgo.com/?q=%s;)
("gmap" . "https://maps.google.com/maps?q=%s;)
("gimages" . "https://google.com/images?q=%s;)
("google" . "https://google.com/search?q=;) ("youtube"
. "https://youtube.com/watch?v=%s;)
("github" . "https://github.com/%s;))
org-agenda-files '("~/org/")
org-capture-templates '(("t" "Personal todo" entry (file+headline
+org-capture-todo-file "Inbox") "* [ ] %?\n%i\n%a" :prepend t)
("n" "Personal notes" entry (file+headline
+org-capture-notes-file "Inbox") "* %u %?\n%i\n%a" :prepend t)
("j" "Journal" entry (file+olp+datetree
+org-capture-journal-file) "* %U %?\n%i\n%a" :prepend t)
("p" "Templates for projects")
("pt" "Project-local todo" entry (file+headline
+org-capture-project-todo-file "Inbox") "* TODO %?\n%i\n%a"
:prepend t)
("pn" "Project-local notes" entry (file+headline
+org-capture-project-notes-file "Inbox") "* %U %?\n%i\n%a"
:prepend t)
("pc" "Project-local changelog" entry (file+headline
+org-capture-project-changelog-file "Unreleased")
"* %U %?\n%i\n%a" :prepend t)
("o" "Centralized templates for projects")
("ot" "Project todo" entry
#'+org-capture-central-project-todo-file "* TODO %?\n %i\n %a" :heading "Tasks"
:prepend
nil)
("on" "Project notes" entry
#'+org-capture-central-project-notes-file "* %U %?\n %i\n %a" :heading "Notes"
:prepend
t)
("oc" "Project changelog" entry
#'+org-capture-central-project-changelog-file "* %U %?\n %i\n %a" :heading
"Changelog" :prepend t)
)
org-persist-after-read-hook '(org-element--cache-persist-after-read)
org-refile-targets '((nil :maxlevel . 3) (org-agenda-files :maxlevel . 3))
org-export-before-parsing-hook '(org-attach-expand-links)
org-cycle-tab-first-hook '(+org-yas-expand-maybe-h +org-indent-maybe-h
org-babel-hide-result-toggle-maybe org-babel-header-arg-expand
+org-clear-babel-results-h
+org-cycle-only-current-subtree-h)
org-default-notes-file "/Users/bytedance/org/notes.org"
org-refile-use-outline-path 'file
org-archive-hook '(org-attach-archive-delete-maybe)
org-file-apps '((remote . emacs) (auto-mode . emacs) (directory . emacs)
("\\.mm\\'" . default) ("\\.x?html?\\'" . default)
("\\.pdf\\'" . default))
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-show-empty-lines
org-cycle-optimize-window-after-visibility-change)
org-persist-before-read-hook '(org-element--cache-persist-before-read)
org-font-lock-set-keywords-hook '(doom-themes-enable-org-fontification)
org-modules '(ol-bibtex)
org-image-actual-width nil
org-attach-use-inheritance t
org-mode-local-vars-hook '(+org-init-gifs-h)
org-mode-hook '(er/add-org-mode-expansions +lookup--init-org-mode-handlers-h
(closure ((hook . org-mode-hook) (--dolist-tail--) t) (
_) (add-hook 'before-save-hook 'org-encrypt-entries nil t))
#[0 "\300\301\302\303\304$\207" [add-hook
change-major-mode-hook org-fold-show-all
Re: commit e22b4eb7 kills formatting & color
Colin Baxter writes: > No, I spoke too soon. That is not the answer. For me using "emacs -q", > an opened org file will expand the folds using but there is still no > synatx coloring. This is probably not relevant but my system is 32bit > not 64. Hmm. I was able to reproduce the issue using some slightly non-standard settings. However, only when there is a popup window asking about non-safe file-local variables. Does it also happen for you after such a popup? Or do you have the settings marked safe? Best, Ihor
Re: [PATCH] lisp/ob-plantuml.el: Insert results in buffer
Joseph Turner writes: > I've added a couple of (message ...) blocks to log the value of > do-export and params. It appears that this combination is producing a > params value which is equivalent to the value of params produced by the > current org-babel-execute:plantuml function. However, when the above > function is executed on a block like: > > #+begin_src plantuml :file "this.png" > Bob->Alice : Hello1! > #+end_src > > I get "Code block produced no output." > > I suspect that setting the scoped params variable has no effect on the > execution of the function, since I can set params to '((:results . > "none")), and I'll still get a printed result if > org-babel-default-header-args:plantuml is set to the above value. This is because you did not really modify the params value. Inserting results happens outside the org-babel-execute:plantuml. You can check out org-babel-execute-src-block function. (params (if do-export (map-merge 'list params '((:results . "file") (:result-params "replace" "file"))) params) This snippet only binds the value locally, restoring it after exiting the let-binding. You may need to modify the params destructively using setf and assq. > Is it safe to modify the value of org-babel-default-header-args:plantuml > from within the function? Would that even work? This is not only unsafe, but will also have no effect on the current execution. The passed params argument is a result of parsing global header args, default header args for specific language, file-local header args, subtree-local header args, and src block-specific header args combined. Strictly speaking, it is normal for org-babel to require the user to specify the output format explicitly via :results output or :results file or any other available setting. Having a :file argument must be accompanied by :results file. However, the ob-plantuml default value makes this generic org-babel requirement not necessary, which was a useful feature as long as only the :file output was supported. The most self-consistent way to introduce non-file output would be changing the default header args for plantuml to nil - it would make things consistent with all other generic backends. Unfortunately, such change is not an option because it will break the existing Org files for users accustomed to :file header arg implying :results file in their existing src blocks. Probably the most consistent way to approach the new output format would be throwing an error if :file is not provided, but :results is set to file. I'd say that it will be much more consistent with other babel backends, albeit less "smart". Best, Ihor
Re: [RFC PATCH] oc-csl: Add support for title, locators and bibentry styles
On Tue, Aug 2, 2022 at 7:14 AM András Simonyi wrote: > the attached patch adds support for three new citation styles which > recently got supported by citeproc-el: > > - cite/title or cite/ti to cite only the title of an item, > - cite/locators or cite/l to cite only the locators, and > - cite/bibentry or cite/b to cite the full bibliography entry. > > I put "RFC" in the subject because I'm not entirely sure about naming > the "bibentry" style, since "bibentry" is natbib terminology, I think, > and biblatex's corresponding command is \fullcite, but I find > "bibentry" slightly more adequate. I agree; there's no ideal name that I can see, and it fits better in the existing style naming scheme. We (well someone :-)) should add the same to the natbib and biblatex processors, though I believe natbib has a wrinkle where you also have to add a preamble line or something. > Also, do we need the "ti" abbreviation for the "title" style? I think so. Bruce
Re: Font-locking lost when using some local variables
Dear Julien, > Julien Cubizolles writes: > With the latest git version of org, all face specifications are > lost in the following org file after the dialog asking about the > unsafe buffer-auto-save-file-name local variable is > answered. Previous versions of org handled it without any problem. > # -*- buffer-auto-save-file-name: nil -*- * Test ** Hello I have experienced the same issue. I reported it yesterday here. The link is https://list.orgmode.org/orgmode/871qu0jo1w@yandex.com/ Best wishes, Colin Baxter.
Font-locking lost when using some local variables
With the latest git version of org, all face specifications are lost in the following org file after the dialog asking about the unsafe buffer-auto-save-file-name local variable is answered. Previous versions of org handled it without any problem. --8<---cut here---start->8--- # -*- buffer-auto-save-file-name: nil -*- * Test ** Hello --8<---cut here---end--->8--- -- Julien Cubizolles
[RFC PATCH] oc-csl: Add support for title, locators and bibentry styles
Dear All,
the attached patch adds support for three new citation styles which
recently got supported by citeproc-el:
- cite/title or cite/ti to cite only the title of an item,
- cite/locators or cite/l to cite only the locators, and
- cite/bibentry or cite/b to cite the full bibliography entry.
I put "RFC" in the subject because I'm not entirely sure about naming
the "bibentry" style, since "bibentry" is natbib terminology, I think,
and biblatex's corresponding command is \fullcite, but I find
"bibentry" slightly more adequate. Also, do we need the "ti"
abbreviation for the "title" style?
thanks and best wishes,
András
From 09b3619693cf4979212d828a0452741e00fca8a4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A1s=20Simonyi?=
Date: Tue, 2 Aug 2022 11:32:17 +0200
Subject: [PATCH] oc-csl: Add support for title, locators and bibentry citation
styles
---
lisp/oc-csl.el | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/lisp/oc-csl.el b/lisp/oc-csl.el
index 0b2fe5c41..d84c97e69 100644
--- a/lisp/oc-csl.el
+++ b/lisp/oc-csl.el
@@ -61,7 +61,10 @@
;; - noauthor (na), including bare (b), caps (c) and bare-caps (bc) variants,
;; - nocite (n),
;; - year (y), including a bare (b) variant,
-;; - text (t). including caps (c), full (f), and caps-full (cf) variants,
+;; - text (t), including caps (c), full (f), and caps-full (cf) variants,
+;; - title (ti), including a bare (b) variant,
+;; - locators (l), including a bare (b) variant,
+;; - bibentry (b), including a bare (b) variant,
;; - default style, including bare (b), caps (c) and bare-caps (bc) variants.
;;
;; Using "*" as a key in a nocite citation includes all available items in
@@ -349,6 +352,21 @@ a property list."
(pcase variant
((or "bare" "b") '(:mode year-only :suppress-affixes t))
(_ '(:mode year-only
+ ;; "bibentry" style
+ (`(,(or "bibentry" "b") . ,variant)
+ (pcase variant
+ ((or "bare" "b") '(:mode bib-entry :suppress-affixes t))
+ (_ '(:mode bib-entry
+ ;; "locators" style
+ (`(,(or "locators" "l") . ,variant)
+ (pcase variant
+ ((or "bare" "b") '(:mode locator-only :suppress-affixes t))
+ (_ '(:mode locator-only
+ ;; "title" style
+ (`(,(or "title" "ti") . ,variant)
+ (pcase variant
+ ((or "bare" "b") '(:mode title-only :suppress-affixes t))
+ (_ '(:mode title-only
;; "text" style.
(`(,(or "text" "t") . ,variant)
(pcase variant
@@ -730,7 +748,10 @@ property list."
(("year" "y") ("bare" "b"))
(("text" "t") ("caps" "c") ("full" "f") ("caps-full" "cf"))
(("nil") ("bare" "b") ("caps" "c") ("bare-caps" "bc"))
-(("nocite" "n"
+(("nocite" "n"))
+(("title" "ti") ("bare" "b"))
+(("bibentry" "b") ("bare" "b"))
+(("locators" "l") ("bare" "b"
(provide 'oc-csl)
;;; oc-csl.el ends here
--
2.25.1
Re: [PATCH] oc-csl: Add support for sub-bibliographies
Dear All, On Sun, 31 Jul 2022 at 04:32, Ihor Radchenko wrote: > Can we then change the oc-biblatex et al defaults to output > \printbibliography[heading=none] > ? > > Best, > Ihor unfortunately, IUC, for bibtex suppressing the heading requires the (possibly local) redefinition of some commands, e.g. \thebibliography or \section which I find too intrusive. For natbib there seems to be a similar situation regarding \bibsection. Because of this I think it'd be more viable to change the "csl" and "basic" processors to produce a section heading by default and provide options to set the title and depth or to suppress it, even if this breaks some extensions/configurations. (BTW, the predecessor of oc-csl, citeproc-org added a section heading and org-ref might be doing so too.) best wishes, András
[BUG] org-forward-sentence does not recognize the end of sentences with footnotes [9.5.4 (N/A @ /gnu/store/zi4gr63h5k2w3y5srydk3k05bjrx9pi9-emacs-org-9.5.4/share/emacs/site-lisp/org-9.5.4/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Dear Org Hackers,
If you go to the first word in the following paragraph and press M-e
(org-forward-sentence), the point jumps to the end of the paragraph. But
it should jump to just after the footnote [fn:23].
If I remove the footnote [fn:23], it correctly jumps to the end of the
first colon:
Die Anzahl und Stärke der Werte ist durch eure
gewählte Machtstufe begrenzt:[fn:23] Ein starker
Wert@@latex:\index{Starker Wert}@@ kostet einen Punkt und ein
überragender Wert@@latex:\index{überragender Wert}@@ drei
Punkte.[fn:133] Starke Werte markiert ihr mit =+=, überragende Werte
mit =++=.
Best wishes,
Arne
Emacs : GNU Emacs 28.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.30,
cairo version 1.16.0)
Package: Org mode version 9.5.4 (N/A @
/gnu/store/zi4gr63h5k2w3y5srydk3k05bjrx9pi9-emacs-org-9.5.4/share/emacs/site-lisp/org-9.5.4/)
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
signature.asc
Description: PGP signature
