[O] [SOLVED] Re: recently header argument :file does not respect :dir anymore
This is solved, I found this problem is on package "ob-async" can't handled the :dir correctly. And it's fixed in latest ob-async now. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Re: [O] Link Bug?
On 1/15/19 4:07 PM, Marco Wahl wrote: > Hi, > > Scott Randby writes: > >> First, I'm using Emacs 26.1 and Org 9.2. >> >> If I have [[./page.html]] in an Org file and I click on the link, >> page.html is opened in my browser, but if I have >> [[./page.html#section]] in the Org file and I click on that link, a >> text file named page.html#section is opened in a buffer instead of a >> page in my browser that starts at the desired place. I'm not sure if >> this is a bug or not, but it isn't the kind of behavior I want. Is >> there any way of getting around this behavior? > > The core of your issue seems to be that one can interpret > "./page.html#section" as filename and also as an anchor in html file > "./page.html". > > Possibly there are clever ways to make the program smarter to detect > links to anchors in html files. > > A way around is to be more explicit in the link. E.g. call a browser > via elisp and use the "file:" protocol: > > [[elisp:(browse-url-firefox "file:///home/webstuff/page.html#section")]] This sort of works, but it doesn't give me the correct link when I export to HTML. I was hoping to check links to anchors in HTML files before exporting to HTML, but maybe that was wishful thinking. Oh well, it is easy enough to check such links after exporting to HTML. I don't know enough elisp to be able to think about making Org smarter. Thanks for the help. Scott
[O] Bug: Can't set org-agenda-follow-indirect in custom agenda command .2 (9.2-elpaplus @ /home/n/.emacs.d/elpa/org-plus-contrib-20181230/)]
I'm trying to create a custom agenda command that starts in follow-mode and
follows indirectly. Starting with follow mode works fine, but
org-agenda-follow-indirect is nil in the resulting org agenda buffer.
Minimal Working Example:
- save the following org txt as a local file
- evaluate the src block
- Expected results:
: Current buffer: *Org Agenda*
: org-agenda-follow-indirect: t
- Actual results:
: Current buffer: *Org Agenda*
: org-agenda-follow-indirect: nil
The results can be confirmed interactively in the resulting agenda buffer
as well. Follow mode is on, but headlines are not being followed
indirectly. Setting org-agenda-follow-indirect to t outside of the
org-agenda-custom-commands settings form works as expected.
---
:PROPERTIES:
#+TITLE: org-agenda-follow-indirect bug
#+STARTUP: showeverything
:END:
* Set up Org agenda custom command
#+begin_src emacs-lisp :var current-file=(list (buffer-file-name))
;;reset global default value just in case
(setq org-agenda-follow-indirect nil)
;;set up org agenda custom command
(setq org-agenda-files current-file
org-agenda-custom-commands
'(("i" "indirect-follow-test" todo ""
((org-agenda-follow-indirect t)
(org-agenda-start-with-follow-mode t)
;;Test values
(org-agenda nil "i")
(set-buffer org-agenda-this-buffer-name)
(message "Current buffer: %s\norg-agenda-follow-indirect: %s"
(current-buffer) org-agenda-follow-indirect)
#+end_src
#+RESULTS:
: Current buffer: *Org Agenda*
: org-agenda-follow-indirect: nil
* TODO TESTS one
** TODO Test heading two
*** TODO Test heading three
Emacs : GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, Xaw3d
scroll bars)
of 2019-01-14
Package: Org mode version 9.2 (9.2-elpaplus @
/home/n/.emacs.d/elpa/org-plus-contrib-20181230/)
current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-refile-targets '((org-agenda-files :maxlevel . 20) (my/org-files-list
:maxlevel . 20))
org-enforce-todo-dependencies t
org-src-tab-acts-natively t
org-agenda-files '("~/Documents/todo")
org-modules '(org-habit)
org-mode-hook '(org-bullets-mode auto-fill-mode writegood-mode
org-indent-mode
flyspell-mode
(closure (t) nil (add-hook 'after-save-hook
'my/org-agenda-redo-all nil t))
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-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
org-journal-update-auto-mode-alist org-eldoc-load)
org-outline-path-complete-in-steps nil
org-archive-hook '(org-attach-archive-delete-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-journal-mode-hook '((lambda nil (auto-fill-mode t) (flyspell-mode t))
(lambda nil
(add-hook org-journal-encrypt-on
'org-journal-encryption-hook nil
t)
)
)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-log-reschedule t
org-agenda-text-search-extra-files '(agenda-archives)
org-babel-pre-tangle-hook '(save-buffer)
org-file-apps '((auto-mode . emacs) ("\\.mm\\'" . default)
("\\.mp \\'" . "/usr/bin/mpv %s")
("\\.x?html?\\'" . "/usr/bin/firefox %s") ("\\.pdf\\'" .
default))
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-babel-load-languages '((js . t) (shell . t) (python . t) (org . t))
org-log-done 'time
org-hide-emphasis-markers t
org-ellipsis "↴"
org-habit-following-days 1
org-agenda-span 'day
org-src-lang-modes '(("arduino" . arduino) ("redis" . redis) ("php" . php)
("C" . c)
("C++" . c++) ("asymptote" . asy) ("bash" . sh)
("beamer" . latex)
("calc" . fundamental) ("cpp" . c++) ("ditaa" .
artist)
("dot" . fundamental) ("elisp" . emacs-lisp) ("ocaml"
. tuareg)
("screen" . shell-script) ("shell" . sh) ("sqlite" .
sql))
org-src-preserve-indentation t
org-habit-today-glyph 128197
org-fontify-done-headline t
org-habit-show-habits-only-for-today nil
org-occur-hook '(org-first-headline-recenter)
org-structure-template-alist '(("se" . "src emacs-lisp") ("a" . "export
ascii")
("c" . "center") ("C" . "comment") ("e" .
"example")
[O] Bug? svg images do not display on modenr browser on export
I think this is a bug but I don't know enough about svg images to be sure. On export, links to svg images produce an element rather than an . Here's the docstring of the function (from ox-heml): - Return \"object\" embedding svg file SOURCE with given ATTRIBUTES. INFO is a plist used as a communication channel. The special attribute \"fallback\" can be used to specify a fallback image file to use if the object embedding is not supported. CSS class \"org-svg\" is assigned as the class of the object unless a different class is specified with an attribute. --- Neither chrome nor firefox can display these objects. On the other hand, if I modify ~org-html--format-image to~ treat svg images just like other images (in an tag) then the image displays just fine. Is there a reason we use the object tag instead/ If not, what's the best solution? I na try to work on a proper fix. Thanks, Matt
Re: [O] please read: bug when marking tasks done
[correction: never mind the ranges part.]
Re: [O] please read: bug when marking tasks done
some possibly obvious observations: nobody will want repeating inactive to be changed by org for the bug case. those are sacrosanct in that sense. but if the variable solution is chosen as the sole solution, setting it to allow changed inactive repeaters will make logbooks no longer reliable. i don't think anybody will want that. "inactive" means "don't show in agenda unless org-agenda-include-inactive-timestamps is non-nil". not "sacrosanct". while i have no use for inactive repeaters, the feature imo should not be reverted. it's a good idea. imagine saying "the next phase of the project will be on ...". for the emphasis solution, not everybody wants the verbatim or code face in the buffer [can be distracting] or on export ["why that particular string?"]. verbatim is not always set to default. some might want to have changed repeating inactive without triggering the bug and also without using the special faces. inactive repeaters can exist if you have active repeater events [bare ts or ranges] and decide to "comment them out" by making them inactive using shift down on the < or >. some probably do this. yet they will not want them changed inadvertently if they set the variable to non-nil and aren't thinking about that. surprise. commented repeater cookies does not have any of the above drawbacks. it might require a 3rd party tool to update its re if that tool uses repeaters. this is not unprecedented. the inactive repeater feature might already require a 3rd party tool to update its re. so upon reflection i think i'd go for commentable repeater cookies. it has a bonus too: whenever you turn off a repeater, it can be annoying that it zeroes out the interval. commenting would fix that. perhaps there is a better, unmentioned solution?
[O] Bug: regression with :export both :noweb strip-export [9.2 (9.2-elpa @ /home/adl/.emacs.d/elpa/org-20181230/)]
Hi!
I have some documentation where I use the noweb syntax to include some
common context in some code fragment I want to discuss. On export
I'd like to display the code fragments without the common context,
followed by their output.
Since I updated to org 9.2, the following idiom stopped working.
--
#+NAME: context
#+BEGIN_SRC C++ :exports none
#include
int u = 0;
#+END_SRC
#+BEGIN_SRC C++ :exports both :noweb strip-export :results verbatim
<>
int main()
{
std::cout << "bar\n";
return u;
}
#+END_SRC
--
Upon export to html I'm expecting to see the second block of code with
<> stripped away, followed by a block of text containing the
result (bar). With Org 9.2 I don't get the latter, because the
compilation of this small program fails during the export. Inspection
of the temporary file passed to the compiler reveals that <>
has been stripped away from the code passed as input to the compiler,
not just from the code displayed in html.
Changing ":exports both" to ":exports results" has the same issue.
Evaluating the code block with C-c C-c works correctly. So it seems to
me that the meaning of "strip-export" was changed from "strip noweb
markers before exporting source blocks" to "strip noweb markers for
source blocks before exporting or even when evaluating them via
:export". Was this meant?
One workaround I have found is to evaluate such code fragments via noweb
instead of via :exports.
--
#+NAME: context2
#+BEGIN_SRC C++ :exports none
#include
int u = 0;
#+END_SRC
#+NAME: bar2
#+BEGIN_SRC C++ :exports code :noweb strip-export :results verbatim
<>
int main()
{
std::cout << "bar\n";
return u;
}
#+END_SRC
#+BEGIN_SRC text :noweb yes
<>
#+END_SRC
--
(This is not exactly equivalent from a CSS point of view, but at least
it exports the output.)
Emacs : GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.2)
of 2018-12-18, modified by Debian
Package: Org mode version 9.2 (9.2-elpa @ /home/adl/.emacs.d/elpa/org-20181230/)
current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-latex-listings 'minted
org-babel-after-execute-hook '((lambda nil (org-redisplay-inline-images)))
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-protocol-default-template-key "w"
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-html-format-inlinetask-function
'org-html-format-inlinetask-default-function
org-src-tab-acts-natively t
org-odt-format-headline-function 'org-odt-format-headline-default-function
org-special-ctrl-a/e t
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-archive-hook '(org-attach-archive-delete-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-startup-with-inline-images t
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-bibtex-headline-format-function #[257 "\300.\236A\207" [:title] 3 "\n\n(fn
ENTRY)"]
org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
org-babel-pre-tangle-hook '(save-buffer)
org-file-apps '(("\\.pdf::\\([[:digit:]]+\\)\\'" . org-pdfview-open)
("\\.pdf\\'" . org-pdfview-open)
(auto-mode . emacs) ("\\.mm\\'" . default) ("\\.x?html?\\'" .
default)
("\\.pdf\\'" . default))
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-babel-load-languages '((shell . t) (python . t) (plantuml . t) (dot . t)
(R . t) (C . t))
org-babel-python-command "/usr/bin/python3"
org-src-lang-modes '(("arduino" . arduino) ("redis" . redis) ("php" . php)
("C" . c) ("C++" . c++)
("asymptote" . asy) ("bash" . sh) ("beamer" . latex)
("calc" . fundamental)
("cpp" . c++) ("ditaa" . artist) ("dot" . fundamental)
("elisp" . emacs-lisp)
("ocaml" . tuareg) ("screen" . shell-script) ("shell" .
sh) ("sqlite" . sql))
org-occur-hook '(org-first-headline-recenter)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-speed-command-hook '(org-speed-command-activate
org-babel-speed-command-activate)
org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
org-babel-tangle-lang-exts '(("D" . "d") ("C++" . "cpp") ("python" . "py")
("emacs-lisp" . "el")
("elisp" . "el"))
org-return-follows-link t
org-confirm-shell-link-function 'yes-or-no-p
org-link-parameters '(("id" :follow org-id-open) ("eww" :follow eww :store
org-eww-store-link)
("rmail" :follow org-rmail-open :store
Re: [O] Link Bug?
Hi, Scott Randby writes: > First, I'm using Emacs 26.1 and Org 9.2. > > If I have [[./page.html]] in an Org file and I click on the link, > page.html is opened in my browser, but if I have > [[./page.html#section]] in the Org file and I click on that link, a > text file named page.html#section is opened in a buffer instead of a > page in my browser that starts at the desired place. I'm not sure if > this is a bug or not, but it isn't the kind of behavior I want. Is > there any way of getting around this behavior? The core of your issue seems to be that one can interpret "./page.html#section" as filename and also as an anchor in html file "./page.html". Possibly there are clever ways to make the program smarter to detect links to anchors in html files. A way around is to be more explicit in the link. E.g. call a browser via elisp and use the "file:" protocol: [[elisp:(browse-url-firefox "file:///home/webstuff/page.html#section")]] HTH -- Marco
[O] Link Bug?
First, I'm using Emacs 26.1 and Org 9.2. If I have [[./page.html]] in an Org file and I click on the link, page.html is opened in my browser, but if I have [[./page.html#section]] in the Org file and I click on that link, a text file named page.html#section is opened in a buffer instead of a page in my browser that starts at the desired place. I'm not sure if this is a bug or not, but it isn't the kind of behavior I want. Is there any way of getting around this behavior? Scott Randby
Re: [O] Clone tree backwards in time
On 1/13/19 8:23 PM, Yasushi SHOJI wrote: > On Thu, Jan 10, 2019 at 1:28 PM Scott Randby wrote: >> On occasion, I need to clone a tree backwards in time. I tried using >> something like -2d (instead of the usual +2d) without success. Is there a >> way to clone backwards in time? > > How about this? Unfortunately, I don't have the knowledge needed to test your patch, but it seems good to me. Any possibility of testing this and maybe incorporating it into Org? Scott
[O] Org Elpa deployment failing for past 2 weeks
Hello, The Org Elpa deploys a new release every week on Mondays. But it looks like that release has been failing for past 2 weeks. Here's the log file from yesterday that shows the error during make cleanall: https://orgmode.org/elpa/build-org-pkg.txt -- Kaushal Modi
Re: [O] please read: bug when marking tasks done
hello, On Sun, Jan 13, 2019 at 3:16 PM Nicolas Goaziou wrote: > Hello, > > cesar mena writes: > > > i'm ok going with the verbatim syntax - rescheduled lines will now look > > like (w/o the double quotes?): > > > > - Rescheduled from =[2019-02-05 Tue .1m]= on [2018-09-29 Sat 18:50] > > Thinking about it, another possibility is to add a variable, e.g., > `org-repeat-inactive-timestamps', letting the user choose what to do > with inactive time stamps. I think it would default to nil. > > This would be a more conservative solution; however, this would > contradict releases notes for Org 9.2. > > WDYT? > > this works of course and it doesn't affect current workflows while allowing for inactive repeating timestamps. the caveat would be that in the case of repeating timestamps, setting both `org-log-into-drawer' and `org-repeat-inactive-timestamps' to a true value will overwrite "Rescheduling" entries from the :LOGBOOK:. in some limited sense the two are incompatible (which would require the verbatim syntax). with that understanding, and the fact that repeating inactive timestamps is a new "feature" my vote is for `org-repeat-inactive-timestamps'. this leaves room down the road, should the need arise, for verbatim syntax in log entries. regards, -cm
Re: [O] recent org-mode changes: completion of repeated tasks reports "10 repeater intervals were not enough to shift date past today"
Daniel Ortmann writes: > No other tasks. Here is the complete text with only one url removed: > > * TODO [#C] p6 time entry > DEADLINE: <2019-01-18 Fri ++1w -0d> > :PROPERTIES: > :LAST_REPEAT: [2019-01-11 Fri 17:03] > :END: > :LOGBOOK: > > On 1/13/19 10:12 AM, Bernt Hansen wrote: > > Daniel Ortmann writes: > > I have a weekly scheduled task with ... > DEADLINE: <2019-01-18 Fri ++1w -0d> > > Recently, when I complete the task it reports the following: > > Clock stopped at [2019-01-11 Fri 17:03] after 0:05 > 10 repeater intervals were not enough to shift date past today. > Continue? (y or n) n > > Thoughts? > > Hi Daniel, > > Do you have some other repeating timestamp buried somewhere in that > task? It is probably moving that one forward and it is the one that > needs more than 10 repeats to become current. > > There was a recent change that updates all repeating timestamps in the > task. > > Regards, > Bernt Sorry I can't reproduce what you are seeing. Regards, Bernt
Re: [O] please read: bug when marking tasks done
Samuel Wales writes: > dunno best solution. > > another option is to comment out repeater intervals like ;.+2d instead > of .+0d or =[... .+2d]=. > > this would also allow you to know what the interval was [currently > that information is lost]. it would avoid overloading face. it would > be under user control for every ts. it would, however, require > updating ts regexp. > > > On 1/13/19, Nicolas Goaziou wrote: >> Hello, >> >> cesar mena writes: >> >>> i'm ok going with the verbatim syntax - rescheduled lines will now look >>> like (w/o the double quotes?): >>> >>> - Rescheduled from =[2019-02-05 Tue .1m]= on [2018-09-29 Sat 18:50] >> >> Thinking about it, another possibility is to add a variable, e.g., >> `org-repeat-inactive-timestamps', letting the user choose what to do >> with inactive time stamps. I think it would default to nil. >> >> This would be a more conservative solution; however, this would >> contradict releases notes for Org 9.2. >> >> WDYT? >> >> Regards, >> >> -- >> Nicolas Goaziou >> >> I don't have a need for updating any timestamps but the ones in the SCHEDULED/DEADLINE: entry. A variable to control behaviour would work great for me. Regards, Bernt
