[O] ox-hugo-like "DWIM" cope for other exporters?
Aloha Matt, I've often wished LaTeX export had this capability. I'd certainly be happy if this were a feature of all the exporters. All the best, Tom
[O] bug#32722: bug#32722: bug#32722: bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?
Eli Zaretskii writes:
>> From: Nicolas Goaziou
>> Cc: r...@gnu.org, 32...@debbugs.gnu.org, n...@flqt.fr, les...@watter.net,
>> right...@gmail.com, kaushal.m...@gmail.com, Rasmus
>> Date: Sat, 29 Sep 2018 20:33:35 +0200
>>
>> > Thank you. Can we have this change on the ermacs-26 branch of Emacs,
>> > please?
>>
>> I don't have access to the Emacs repository.
>>
>> You can either give me write access there, or I can send you the Texinfo
>> @node contents, or someone with write access could do it for us. I'm
>> Cc'ing Rasmus for the last option.
>
> I could install a patch that you produced from the Org repository's
> appropriate branch.
>
> Thanks.
I've tried to combine these org-manual.org changes into a patch for
org.texi. This patch should apply on the emacs-26 branch.
-- >8 --
Subject: [PATCH] org.texi: Rewrite Org Mobile section
* doc/misc/org.texi (Org Mobile): Rewrite from "MobileOrg" section.
Remove all references to non-free software. Move into
"Miscellaneous".
This reflects Nicolas Goaziou's changes from Org's b929e5d77,
46b49ab57, and 3f826b9f7.
---
doc/misc/org.texi | 293 --
1 file changed, 152 insertions(+), 141 deletions(-)
diff --git a/doc/misc/org.texi b/doc/misc/org.texi
index 60647e65e8..873ce4d2cd 100644
--- a/doc/misc/org.texi
+++ b/doc/misc/org.texi
@@ -325,7 +325,6 @@ Top
* Working with source code::Export, evaluate, and tangle code blocks
* Miscellaneous:: All the rest which did not fit elsewhere
* Hacking:: How to hack your way around
-* MobileOrg:: Viewing and capture on a mobile device
* History and acknowledgments:: How Org came into being
* GNU Free Documentation License:: The license for this documentation.
* Main Index:: An index of Org's concepts and features
@@ -760,12 +759,19 @@ Top
* TTY keys::Using Org on a tty
* Interaction:: With other Emacs packages
* org-crypt:: Encrypting Org files
+* Org Mobile:: Viewing and capture on a mobile device
Interaction with other packages
* Cooperation:: Packages Org cooperates with
* Conflicts:: Packages that lead to conflicts
+Org Mobile
+
+* Setting up the staging area:: For the mobile device
+* Pushing to the mobile application:: Uploading Org files and agendas
+* Pulling from the mobile application:: Integrating captured and flagged items
+
Hacking
* Hooks:: How to reach into Org's internals
@@ -788,12 +794,6 @@ Top
* Translator functions::Copy and modify
* Radio lists:: Sending and receiving lists
-MobileOrg
-
-* Setting up the staging area:: For the mobile device
-* Pushing to MobileOrg::Uploading Org files and agendas
-* Pulling from MobileOrg:: Integrating captured and flagged items
-
@end detailmenu
@end menu
@@ -17253,6 +17253,7 @@ Miscellaneous
* TTY keys::Using Org on a tty
* Interaction:: With other Emacs packages
* org-crypt:: Encrypting Org files
+* Org Mobile:: Viewing and capture on a mobile device
@end menu
@@ -18187,6 +18188,150 @@ org-crypt
Excluding the crypt tag from inheritance prevents encrypting previously
encrypted text.
+@node Org Mobile
+@section Org Mobile
+
+@cindex smartphone
+
+Org Mobile is a protocol for synchronizing Org files between Emacs and
+other applications, e.g., on mobile devices. It enables offline-views
+and capture support for an Org mode system that is rooted on a ``real''
+computer. The external application can also record changes to
+existing entries.
+
+This appendix describes Org's support for agenda view formats
+compatible with Org Mobile. It also describes synchronizing changes,
+such as to notes, between the mobile application and the computer.
+
+To change tags and TODO states in the mobile application, first
+customize the variables @code{org-todo-keywords} and @code{org-tag-alist}.
+These should cover all the important tags and TODO keywords, even if
+Org files use only some of them. Though the mobile application is
+expected to support in-buffer settings, it is required to understand
+TODO states @emph{sets} (see @ref{Per-file keywords}) and
+@emph{mutually exclusive} tags (see @ref{Setting tags}) only for those set in
+these variables.
+
+@menu
+* Setting up the staging area:: For the mobile device
+* Pushing to the mobile application:: Uploading Org files and agendas
+* Pulling from the mobile application:: Integrating captured and flagged items
+@end menu
+
+@node Setting up the staging area
+@subsection Setting up the staging area
+
+@vindex org-mobile-directory
+The mobile application needs access to a file directory on
+a server@footnote{For a server to host files, consider using a WebDAV server,
+such as @uref{https://nextcloud.com, Nextcloud}.
Re: [O] can capture create search links?
hi j, thanks for commenting. i use org-id extensively. however, if i am just capturing a note on an org entry that does not already have an org-id, i want the link so that i have context for what i am talking about, but i do not want to create an org-id. org-id for this purpose would clutter org too much, as it would create an org-id for every tiny little teensy org entry. that is why i want %a [or something similar] to create a search link for the header text, which searches all agenda files and text search extra files [not just the current file]. that would give me the context i need, with a mostly-unbreakable link [i don't need perfection in this case], that tells me where i was when i made the note. although i use org-id extensively, i don't want to use org-id for this. samuel
[O] [patch] Problems producing TikZ PNGs from LaTeX src blocks (was: Problems producing TikZ PNGs from LaTeX src blocks)
Eric S Fraga writes:
> On Friday, 28 Sep 2018 at 11:39, Christian Moe wrote:
>> Hi,
>>
>> I am trying to generate a PNG file with a TikZ picture from a LaTeX src
>> block, looking at instructions here:
>> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html
>>
>> I try this:
>>
>> #+header: :file "tikzpic.png" :fit yes :results raw file :exports results
>> :headers '("\\usepackage{tikz}")
>> #+begin_src latex
>> \begin{tikzpicture}
>>\draw [fill=green] (0,4) -- (3,0) -- (-3,0) -- cycle;
>> \end{tikzpicture}
>> #+end_src
It seems that the function `org-babel-execute:latex' ignores the
property :headers under certain circumstances. Therefore the line
"\usepackage{tikz}" will be missing in your resulting latex document.
The property is not ignored if you also append the property
":imagemagick t" to the #+header line. So you can use the following
header as a fix (for another fix, see below):
#+header: :file "tikzpic.png" :fit yes :results raw file :exports results
:headers '("\\usepackage{tikz}") :imagemagick t
I've drafted a patch that fixes the issue. I would appreciate if some
maintainer could have a look and comment, or apply the patch:
>From a54f83d2b411ae58941c32cb23fd47f38e70dc80 Mon Sep 17 00:00:00 2001
From: Benjamin Motz
Date: Fri, 28 Sep 2018 16:32:59 +0200
Subject: [PATCH 1/2] Fix ob-latex to respect the keyword :headers
This adds support for property :headers in org-format-latex-options.
TINYCHANGE
---
lisp/ob-latex.el | 8 ++--
lisp/org.el | 3 +++
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/lisp/ob-latex.el b/lisp/ob-latex.el
index 8d037090e..19e44dee5 100644
--- a/lisp/ob-latex.el
+++ b/lisp/ob-latex.el
@@ -108,8 +108,12 @@ This function is called by `org-babel-execute-src-block'."
(append (cdr (assq :packages params)) org-latex-packages-alist)))
(cond
((and (string-suffix-p ".png" out-file) (not imagemagick))
- (org-create-formula-image
- body out-file org-format-latex-options in-buffer))
+ (let ((latex-options (copy-tree org-format-latex-options)))
+ (when headers
+ (plist-put latex-options :headers
+ (append (plist-get latex-options :headers) headers)))
+(org-create-formula-image
+ body out-file latex-options in-buffer)))
((string-suffix-p ".tikz" out-file)
(when (file-exists-p out-file) (delete-file out-file))
(with-temp-file out-file
diff --git a/lisp/org.el b/lisp/org.el
index f3a19d643..d2ff4e41c 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -18571,6 +18571,9 @@ a HTML file."
(if (string= bg "Transparent") "white" bg
(with-temp-file texfile
(insert latex-header)
+ (when-let ((headers (plist-get options :headers)))
+ (dolist (h headers)
+ (insert h)))
(insert "\n\\begin{document}\n"
"\\definecolor{fg}{rgb}{" fg "}\n"
"\\definecolor{bg}{rgb}{" bg "}\n"
--
2.18.0
> This works for me, cutting and pasting exactly what you have posted into a
> small org file.
You probably have "\\usepackage{tikz}" set in your variable
`org-format-latex-header' (another fix for the issue).
> Output from my *Messages* buffer:
> ,
> | Wrote /tmp/x.org
> | org-babel-exp process latex at position 128...
> | Evaluate this latex code block on your system? (y or n) y
> | executing Latex code block...
> | (Shell command succeeded with no output)
> | Code block evaluation complete.
> | Local Ispell dictionary set to british
> | Saving file /tmp/x.tex...
> `
> when I export to LaTeX. What does your message log say?
Actually, the output looks identical when the command indeed fails to
run latex without errors - the output file is generated nonetheless and
the user thinks everything is ok. I'd suggest to add '-halt-on-error' to
avoid creating an output file. This will then signal an error to the
user. A possible patch is appended:
>From 9f08a34c7eddfea394b9a1e78d54b3b26b139b51 Mon Sep 17 00:00:00 2001
From: Benjamin Motz
Date: Sat, 29 Sep 2018 22:15:39 +0200
Subject: [PATCH 2/2] preview-latex: don't produce output file on error
This will result in an error-message visible to the user. Otherwise,
the user might just assume that everything went ok, even though there
were issues when creating the output file.
TINYCHANGE
---
lisp/org.el | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index d2ff4e41c..0c7358eb0 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -3939,7 +3939,7 @@ All available processes and theirs documents can be found in
:image-input-type "dvi"
:image-output-type "png"
:image-size-adjust (1.0 . 1.0)
- :latex-compiler ("latex -interaction nonstopmode -output-directory %o %f")
+ :latex-compiler ("latex -interaction nonstopmode -halt-on-error -output-directory %o %f")
:image-converter ("dvipng -fg %F -bg %B -D %D -T tight -o %O %f"))
(dvisvgm
:programs ("latex" "dvisvgm")
@@ -3949,7
[O] can capture create search links?
Hi Samuel, as to org I only have user status, so there may be better solutions for you. Am 29.09.18 um 00:20 schrieb Samuel Wales: > what i'd like is for capture to produce a link that, when clicked, > will search through my agenda files and text search extra files for a > matching header. I use IDs for that purpose. In my config file I added (require 'org-id) (setq org-id-link-to-org-use-id 'create-if-interactive-and-no-custom-id) In all capture templates, IDs are automatically added by adding, immediately after the heading and a possible scheduling line, ":PROPERTIES:\n:ID: %(org-id-new)\n:END:\n" within the template string. With this, %a in the template string is replaced by that ID if the ID exists. The ID survives refiling. Hope that helps, Julius
Re: [O] Concatenating Org property values from parent subtrees
Hello, Michael Welle writes: [...] > (defun hmw/org-prop-append(prop value) > (save-excursion > (org-up-heading-safe) > (format "%s %s" value (cdr (assq prop >(car > (org-babel-params-from-properties))) > > (defalias 'A 'hmw/org-prop-append) and I just realise that it works with code blocks only. I guess the way to get general property values has to be adapted. Regards hmw
Re: [O] Concatenating Org property values from parent subtrees
Hello, Kaushal Modi writes: > On Sat, Sep 29, 2018 at 2:39 PM Michael Welle wrote: > >> >> I asked something similar earlier this year (concatenating compiler >> flags given as header-args property, used for linking against different >> libs in different sections of the Org file). I ended with a function >> that grabs the current property value and returns the value concatenated >> with new value. That function can be used as a 'property value'. That's >> not a nice and bullet proof solution, but works good enough to me to >> generate the solutions to the psets for the lecture. >> > > Please share it if you don't mind. I plan to use it or its derivative in > ox-hugo. The property is planned to be a path property, and with nested > property values of "a","b" and "c", which I want to parse as "a/b/c". (defun hmw/org-prop-append(prop value) (save-excursion (org-up-heading-safe) (format "%s %s" value (cdr (assq prop (car (org-babel-params-from-properties))) (defalias 'A 'hmw/org-prop-append) I use it like this: * foo :PROPERTIES: :header-args: :flags -Wall :END: ** bar #+begin_src C :flags (A :flags "-lm") #+end_src ** baz :PROPERTIES: :header-args: :flags (A :flags "-lcunit") :END: #+begin_src C #+end_src Regards hmw
Re: [O] Concatenating Org property values from parent subtrees
On Sat, Sep 29, 2018 at 2:39 PM Michael Welle wrote: > > I asked something similar earlier this year (concatenating compiler > flags given as header-args property, used for linking against different > libs in different sections of the Org file). I ended with a function > that grabs the current property value and returns the value concatenated > with new value. That function can be used as a 'property value'. That's > not a nice and bullet proof solution, but works good enough to me to > generate the solutions to the psets for the lecture. > Please share it if you don't mind. I plan to use it or its derivative in ox-hugo. The property is planned to be a path property, and with nested property values of "a","b" and "c", which I want to parse as "a/b/c".
[O] bug#32722: bug#32722: bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?
> From: Nicolas Goaziou > Cc: r...@gnu.org, 32...@debbugs.gnu.org, n...@flqt.fr, les...@watter.net, > right...@gmail.com, kaushal.m...@gmail.com, Rasmus > Date: Sat, 29 Sep 2018 20:33:35 +0200 > > > Thank you. Can we have this change on the ermacs-26 branch of Emacs, > > please? > > I don't have access to the Emacs repository. > > You can either give me write access there, or I can send you the Texinfo > @node contents, or someone with write access could do it for us. I'm > Cc'ing Rasmus for the last option. I could install a patch that you produced from the Org repository's appropriate branch. Thanks.
Re: [O] Concatenating Org property values from parent subtrees
Hello, Kaushal Modi writes: > Hello, > > Is there a way to achieve something like below? See the content in each > nested subtree in the example below. I asked something similar earlier this year (concatenating compiler flags given as header-args property, used for linking against different libs in different sections of the Org file). I ended with a function that grabs the current property value and returns the value concatenated with new value. That function can be used as a 'property value'. That's not a nice and bullet proof solution, but works good enough to me to generate the solutions to the psets for the lecture. Regards hmw
[O] bug#32722: bug#32722: bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?
Hello, Eli Zaretskii writes: > Thank you. Can we have this change on the ermacs-26 branch of Emacs, > please? I don't have access to the Emacs repository. You can either give me write access there, or I can send you the Texinfo @node contents, or someone with write access could do it for us. I'm Cc'ing Rasmus for the last option. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] Bug: org-agenda-filter-by-top-heading does not filter [9.1.14 (release_9.1.14-908-gf1269e)]
Hello, That is exactly what happened. I reread the helper and now it is obvious that "Root" is among the parents also. I didn't realized that at the time. Thanks Kyle and Adrian for the clarification. Lem On Sun, Sep 16, 2018 at 4:29 PM Kyle Meyer wrote: > Hello, > > Lem Ming writes: > > > In the agenda list `org-agenda-list` buffer, when I do > > `org-agenda-filter-by-top-headline` when the point is over a line with a > > headline, nothing is filtered. > > > > I've never used org-agenda-filter-by-top-headline, but taking a quick > look at it and its helper, org-find-top-headline, the intention seems to > be to find the level-one parent of the current heading. So, in your > example, > > > * Root > > ** TODO task 2 > > :tag_2: > >DEADLINE: <2018-09-14 Fri 12:00:00> > >:PROPERTIES: > >:ADD_TIME: <2018-09-07 Fri 23:47:00> > >:END: > > *** TODO task 2.1 > > DEADLINE: <2018-09-14 Fri 11:00:00> > > :PROPERTIES: > > :ADD_TIME: <2018-09-07 Fri 23:47:00> > > :END: > [...] > > ** TODO task 7 > >DEADLINE: <2018-09-14 Fri 12:00:00> SCHEDULED: <2018-09-12 Wed > 10:00:00> > > ... it'd find "Root" if point were on any of the tasks. If I'm reading > your report correctly, you're assuming that with point on the "task 2", > it'd take *that* as the top-level heading and filter to all the tasks > under it (task 2.1, etc). Instead, it finds "Root" and filters to > everything thing under that, which---in your example file---is the same > thing, so you don't see any change. > > -- > Kyle >
[O] bug#32722: bug#32722: bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?
> From: Nicolas Goaziou > Date: Sat, 29 Sep 2018 16:53:04 +0200 > Cc: 32...@debbugs.gnu.org, n...@flqt.fr, les...@watter.net, > right...@gmail.com, > kaushal.m...@gmail.com > > > This is actually good news. It means Android MobileOrg is almost ok. > > If someone wants to do a little work on Android MobileOrg, so it could > > go into f-droid, we could recommend its use. But the doc should be > > updated. > > For the record, I rewrote the section about Org Mobile in the manual. > This removed all instances of "MobileOrg" and "Dropbox". Thank you. Can we have this change on the ermacs-26 branch of Emacs, please?
[O] bug#32722: bug#32722: bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?
Hello, Richard Stallman writes: > This is actually good news. It means Android MobileOrg is almost ok. > If someone wants to do a little work on Android MobileOrg, so it could > go into f-droid, we could recommend its use. But the doc should be > updated. For the record, I rewrote the section about Org Mobile in the manual. This removed all instances of "MobileOrg" and "Dropbox". Here it is in its full glory (please ignore the broken links, which refer to other parts in the Org manual): --8<---cut here---start->8--- ━ ORG MOBILE Release 9.2 The Org Mode Developers ━ Table of Contents ─ 1. Setting up the staging area 2. Pushing to the mobile application 3. Pulling from the mobile application Org Mobile is a protocol for synchronizing Org files between Emacs and other applications, e.g., on mobile devices. It enables offline-views and capture support for an Org mode system that is rooted on a “real” computer. The external application can also record changes to existing entries. This appendix describes Org’s support for agenda view formats compatible with Org Mobile. It also describes synchronizing changes, such as to notes, between the mobile application and the computer. To change tags and TODO states in the mobile application, first customize the variables `org-todo-keywords' and `org-tag-alist'. These should cover all the important tags and TODO keywords, even if Org files use only some of them. Though the mobile application is expected to support in-buffer settings, it is required to understand TODO states /sets/ (see [BROKEN LINK: *Setting up keywords for individual files]) and /mutually exclusive/ tags (see [BROKEN LINK: *Setting Tags]) only for those set in these variables. 1 Setting up the staging area ═ The mobile application needs access to a file directory on a server[1] to interact with Emacs. Pass its location through the `org-mobile-directory' variable. If you can mount that directory locally just set the variable to point to that directory: ┌ │ (setq org-mobile-directory "~/orgmobile/") └ Alternatively, by using TRAMP (see [TRAMP User Manual]), `org-mobile-directory' may point to a remote directory accessible through, for example, SSH and SCP: ┌ │ (setq org-mobile-directory "/scpc:u...@remote.host:org/webdav/") └ With a public server, consider encrypting the files. Org also requires OpenSSL installed on the local computer. To turn on encryption, set the same password in the mobile application and in Emacs. Set the password in the variable `org-mobile-use-encryption'[2]. Note that even after the mobile application encrypts the file contents, the file name remains visible on the file systems of the local computer, the server, and the mobile device. [TRAMP User Manual] 2 Pushing to the mobile application ═══ The command `org-mobile-push' copies files listed in `org-mobile-files' into the staging area. Files include agenda files (as listed in `org-agenda-files'). Customize `org-mobile-files' to add other files. File names are staged with paths relative to `org-directory', so all files should be inside this directory[3]. Push creates a special Org file `agendas.org' with custom agenda views defined by the user[4]. Finally, Org writes the file `index.org', containing links to other files. The mobile application reads this file first from the server to determine what other files to download for agendas. For faster downloads, it is expected to only read files whose checksums[5] have changed. 3 Pulling from the mobile application ═ The command `org-mobile-pull' synchronizes changes with the server. More specifically, it first pulls the Org files for viewing. It then appends captured entries and pointers to flagged or changed entries to the file `mobileorg.org' on the server. Org ultimately integrates its data in an inbox file format, through the following steps: 1. Org moves all entries found in `mobileorg.org'[6] and appends them to the file pointed to by the variable `org-mobile-inbox-for-pull'. It should reside neither in the staging area nor on the server. Each captured entry and each editing event is a top-level entry in the inbox file. 2. After moving the entries, Org processes changes to the shared files. Some of them are applied directly and without user interaction. Examples include changes to tags, TODO state, headline and body text. Entries requiring further action are tagged as `FLAGGED'. Org marks entries with problems with an error message in the inbox. They have to be resolved manually. 3.
[O] [PATCH] doc/org-manual→ Intro→ Activation: add space in the command binding
… otherwise emacs 26.1 says “error: C- must prefix a single character” --- doc/org-manual.org | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index ed59adca6..888b60596 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -185,9 +185,9 @@ to globally available keys, like the ones reserved for users (see bindings, please modify the keys to your own liking. #+begin_src emacs-lisp -(global-set-key "\C-cl" 'org-store-link) -(global-set-key "\C-ca" 'org-agenda) -(global-set-key "\C-cc" 'org-capture) +(global-set-key "\C-c l" 'org-store-link) +(global-set-key "\C-c a" 'org-agenda) +(global-set-key "\C-c c" 'org-capture) #+end_src #+cindex: Org mode, turning on -- 2.19.0.dirty
[O] HTML Export - Footnotes inconcistency
Hello, I came across this problem today (or maybe it is intended but I couldn't find any explanation in the docs). There is an inconsistency on how inline/anonymous and named footnotes are exported in HTML. For example, with the following source: --8<---cut here---start->8--- #+TITLE: Testing footnotes #+LANGUAGE: en Testing[fn::test1] footnotes[fn:2] [fn:2] test2 --8<---cut here---end--->8--- Exports to this : --8<---cut here---start->8--- Footnotes: 1 test1 2 test2 --8<---cut here---end--->8--- We can see here that the named footnote creates a paragraph of the same class as the parent container "footpara" whereas the inlined one doesn't create this. If this is intended, why? If not, which is the intended one? Reagards. -- Matthias Paulmier
Re: [O] org-end-of-line and in table interaction
Nicolas Goaziou writes: > Robert Pluim writes: > >> It does call 'end-of-line'. If thatʼs the intended semantics, itʼs not >> entirely clear from the docstring (and I will adjust my code). > > The first sentence is: > > Go to the end of line, but before ellipsis, if any. > > If you think that's ambiguous, would you want to suggest a different > wording? Or do you think we should add a more explicit reference to > `end-of-line' function somewhere in the docstring? I thought it was for headlines only because the next paragraph talks about headlines, but that was entirely my misreading. Robert
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
>> Then saving should be the default again, and not saving optional. > > I believe this would be the best option. Very, very strongly concur with this belief.
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
On Saturday, 29 Sep 2018 at 08:31, Nicolas Goaziou wrote: > Then saving should be the default again, and not saving optional. I believe this would be the best option. -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-783-g97fac4
Re: [O] Bug: utf-8 support for ob-dot.el [9.1.14 (9.1.14-1-g4931fc-elpa @ c:/Users/sig/emacs261/.emacs.d/elpa/org-9.1.14/)]
Sigmund Tzeng writes: > I get your point. The git diff order is wrong. Here it is: Applied. I added a proper commit message. Thank you.
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
Kaushal Modi writes: > Sorry. Here's the original thread: > https://lists.gnu.org/r/emacs-orgmode/2018-04/msg00204.html Thank you. > My email client shows the whole thread from then to now, so I forgot > pasting that. Mine (Gnus) also used to, but, for some reason, it doesn't anymore. > That's a valid concern, though I see the risk of losing unsaved data as > higher than that. Then saving should be the default again, and not saving optional. What about introducing a :no-save keyword in capture templates? It could be useful when the capture target is a remote file, as the OP noted, or when you simply want to handle buffer saving manually. Regards,
