Re: [O] Emacs-orgmode Digest, Vol 159, Issue 29
Hey Niko! I have to admit I grabbed org-contacts to solve my addressbook problem because I had thought BBDB was non-supported these days (and possibly overkill for my use case), though just noted from the other post in the digest that there is an EIEIO re-write. So, may check that out this weekend. Git cloning the code for BBDB from GH I could not find the (org-bbdb-anniversaries-future) function in the BBDB code base (since I thought of just applying it to this use case for org-contacts rather than switching to BBDB). Is that something custom you wrote to support this? If so, could you post it (or mail direct to me?) if you're willing to share? I will be taking a look at EBDB this weekend to see if that might do what I want better (and since it has a nice import function.)... =] thanks! Daryl PS> I have to admit though being a little confused at how the emacs diary works versus org-agenda though I know they interoperate... the simple entries I make which have `<2019-05-29>` type entries in them in my text org file named cal.org, so worried my lack of understanding of emacs internals may be having me conflating things that replace each other. Emacs seems a deep deep rabbit hole at times for us (relative) newbies On Wed, May 29, 2019 at 12:01 AM wrote: > > > Today's Topics: >5. Re: Advance notice of birthdays in org-mode via org-contacts > (Nick Dokos) > -- > > Message: 5 > Date: Mon, 27 May 2019 22:05:07 -0400 > From: Nick Dokos > To: emacs-orgmode@gnu.org > Subject: Re: [O] Advance notice of birthdays in org-mode via > org-contacts > Message-ID: <87lfyrl4fg@alphaville.usersys.redhat.com> > Content-Type: text/plain; charset=utf-8 > > Daryl Manning writes: > > > I'm trying to come up with a better way to give myself advanced notice > on some peoples' birthdays coming up.? > > > > Right now, I use the following in a `cal.org` file to give me notice in > agenda that birthdays are coming up: > > > > ``` > > * BDays ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > ? ? ? ? :bday: > > %%(org-contacts-anniversaries "BIRTHDAY") > > ``` > > > > The generally feeds off a `contacts.org` entry of the nature: > > > > ``` > > *** John Wick? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? > > :PROPERTIES: > > :EMAIL: therealj...@notthepuppy.com > > :BIRTHDAY: 1975-06-06 > > :END: > > ``` > > > > What I'd like is to get, on virtually all birthdays , a week's notice > through due soon (which I'll sort out in org-super-agenda in the view). > Alternatively, is there a nicer way to tag or > > otherwise note some birthdays in the `contacts.org` so that I could > note special people (close friends, family, etc) where I could set a > specific advanced notice period so that I have time > > to do something special for them etc? > > > > Would love to hear peoples' approaches to this. In general, if I'm not > looking out 2 weeks ahead (I spend most time in the day view), I can get > surprised. > > > > I use bbdb, not org-contacts, and I have this in one of my agenda files: > > * Anniversaries >:PROPERTIES: >:CATEGORY: Anniv >:ID: 409062f6-6cb1-467f-b192-2dfcb7b384ca >:END: > %%(org-bbdb-anniversaries-future) > > That gives me the default 7 days of warning, but you can pass an > argument to it to specify the number of days of warning. > > The function is fairly generic, so it should be possible to adapt it > to org-contacts with some modifications. > > -- > Nick > > End of Emacs-orgmode Digest, Vol 159, Issue 29 > ** >
[O] Outdated manual web pages left in place WAS: Re: Problems with inline source blocks
The OP cited this web page: https://orgmode.org/manual/Exporting-code-blocks.html but the link from https://orgmode.org/#docs to the manual eventually leads this web page: https://orgmode.org/manual/Exporting-Code-Blocks.html which is different (note capitalization of "Code" and "Blocks"). I guess that capitalizing the words in the web page URL leaves the outdated page in place. HTH, Chuck
[O] A recent fix caused other face highlighting issue
This commit "42abf5c6954dee8410e33d0c5140d3b36c9d1c15" try to fix org-do-emphasis-faces function on strike-through fontification on heading. But it failed on verbatim like ~code~, =verbatim= etc. Can it be reverted? or provide another solution? -- [ 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] Show APPTs every day in Agneda
Neil Jerram writes: > #+BEGIN_EXAMPLE > ** Bank holiday weekend > > <2018-05-05 Sat>--<2018-05-07 Mon> > #+END_EXAMPLE > Sorry, that's no solution for you, but maybe there's a clue in the > detail there? Ha! - indeed. It's obviously not allowed to add spaces like I used to do: <2018-05-05 Sat> -- <2018-05-07 Mon> With <2018-05-05 Sat>--<2018-05-07 Mon> it works like I want. So, thank you very much to pointing me into the right direction. But this doesn't seem to be documented...(question to all)? Thanks, Michael.
Re: [O] Show APPTs every day in Agneda
On Mon, 27 May 2019 at 23:25, Michael Heerdegen wrote: > Neil Jerram writes: > > > Hi Michael, > > Hi Neil! > > > I'm not in front of my computer, to check this, but I think that an > > active date range will have this effect, i.e. > > > > ** Vacation > > -- > > Hmm, no, AFAICT that's what I used to do, and it only shows the > appointment at start and end date, not between the two dates. That's > with C-c a a btw. I wonder why it seems to work for you... > I've just checked that it really does work for me - and yes, it does. This is a bit of one of my org files: #+BEGIN_EXAMPLE ** Bank holiday weekend <2018-05-05 Sat>--<2018-05-07 Mon> #+END_EXAMPLE and here's (part of) my agenda buffer for that month: #+BEGIN_EXAMPLE Saturday5 May 2018 divorce:(1/3): Bank holiday weekend Sunday 6 May 2018 divorce:(2/3): Bank holiday weekend Monday 7 May 2018 W19 divorce:(3/3): Bank holiday weekend #+END_EXAMPLE Sorry, that's no solution for you, but maybe there's a clue in the detail there? Best wishes, Neil
Re: [O] Capture with date prompt defaults to yesterday
On Sun, 19 May 2019 at 14:36, Neil Jerram wrote:
> I have a capture template like this:
>
> '(org-capture-templates
>(quote
> (("a" "" entry
> (file "~/org/capture.org")
> "** TODO %?
> SCHEDULED: %^t"
>
> When I use that, the date prompt defaults to yesterday, whereas I'd expect
> it to default to today.
>
> I believe this is because I also have (setq org-extend-today-until 2).
> What happens is that (org-get-cursor-date) gets the right _date_, then
> converts that to a time at midnight, i.e. 00:00. And then, I
> presume, some following code thinks that means -1, because of my
> org-extend-today-until setting.
>
> Thoughts?
>
> Many thanks,
>Neil
>
Well I think it's a bug and propose the attached fix. Please let me know
what you think.
Neil
From d52c66f4e4f1fead135427d2c638890b5c7ab224 Mon Sep 17 00:00:00 2001
From: Neil Jerram
Date: Tue, 28 May 2019 21:01:17 +0100
Subject: [PATCH] Make capture's idea of the current day more intuitive
---
lisp/org.el | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index c6861dc9a..763eb1e45 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -18936,7 +18936,9 @@ Returns the number of empty lines passed."
This works in the calendar and in the agenda, anywhere else it just
returns the current time.
If WITH-TIME is non-nil, returns the time of the event at point (in
-the agenda) or the current time of the day."
+the agenda) or the current time of the day; otherwise returns 12pm
+on the cursor date. (Returning 12pm instead of 12am here avoids
+problems of interpretation with respect to `org-extend-today-until'.)"
(let (date day defd tp hod mod)
(when with-time
(setq tp (get-text-property (point) 'time))
@@ -18949,13 +18951,13 @@ the agenda) or the current time of the day."
(cond
((eq major-mode 'calendar-mode)
(setq date (calendar-cursor-to-date)
- defd (encode-time 0 (or mod 0) (or hod 0)
+ defd (encode-time 0 (or mod 0) (or hod 12)
(nth 1 date) (nth 0 date) (nth 2 date
((eq major-mode 'org-agenda-mode)
(setq day (get-text-property (point) 'day))
(when day
(setq date (calendar-gregorian-from-absolute day)
- defd (encode-time 0 (or mod 0) (or hod 0)
+ defd (encode-time 0 (or mod 0) (or hod 12)
(nth 1 date) (nth 0 date) (nth 2 date))
(or defd (current-time
--
2.17.1
Re: [O] manual errata
Hi Nicholas, I have found the manual version in the repo. You are correct. Will check repo version next time. Best, Ian On Tue, May 28, 2019 at 8:31 AM Ian Garmaise wrote: > Hi Nicholas, it is shown on this page. Is there a more up to date version > of the manual I should reference? > > > > https://orgmode.org/manual/Inserting-deadline_002fschedule.html#Inserting-deadline_002fschedule > > > Best, > > Ian > > > On Tue, May 28, 2019 at 5:00 AM Nicolas Goaziou > wrote: > >> Hello, >> >> Ian Garmaise writes: >> >> > org 9.2 pdf manual >> > >> > In Chapter 8, p. 78 >> > >> > function org-mark-entry-for-agenda action >> > C-c C-x C-k >> > >> > This function doesn't exist in my version of org-mode (9.2.3) >> >> I cannot find any reference to this function in current manual. >> >> Regards, >> >> -- >> Nicolas Goaziou >> > > > -- > = > Ian Garmaise > Consultant > Phorix Solutions Group > ia...@phorixsol.com > Toronto cell: 416.432.2251 > NYC: 917.512.9535 > > https://www.linkedin.com/in/igarmaise/ > > http://www.PhorixSol.com > -- = Ian Garmaise Consultant Phorix Solutions Group ia...@phorixsol.com Toronto cell: 416.432.2251 NYC: 917.512.9535 https://www.linkedin.com/in/igarmaise/ http://www.PhorixSol.com
Re: [O] [PATCH] org-clock.el: Fix restore of frame-title-format
Hello, Andrii Kolomoiets writes: > * lisp/org-clock.el (org-frame-title-format-backup): Use nil as initial value. > (org-clock-in): set `org-frame-title-format-backup' to `frame-title-format'. > (org-clock-restore-frame-title-format): New function. > (org-clock-out): Use it. > (org-clock-cancel): Use it. > > The problem was that the `org-frame-title-format-backup' variable is > initialized on org-clock.el loading and future changes to `frame-title-format' > is ignored. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] suppress leading ":" in org-babel output
> On May 27, 2019, at 7:17 PM, Nick Dokos wrote:
>
> Jeremie Juste writes:
>
>> Hello,
>>
>> I recall seeing this thread on the mailing list but I cannot find it
>> back.
>>
>> I would like to suppress the first line leading ":" in the following output
>>
>>
>> #+NAME:mean_purchase_per_shopping_trip
>>
>> #+BEGIN_SRC R :var x=6 :results output :session *R*
>> a <-sprintf("%.2f",12.234324)
>> cat(a,sep="\n")
>> #+END_SRC
>>
>> #+RESULTS: mean_purchase_per_shopping_trip
>> :
>>
>> : 12.23
>>
>
> FWIW, I just get the last line:
>
> #+NAME:mean_purchase_per_shopping_trip
>
> #+BEGIN_SRC R :var x=6 :results output :session *R*
> a <-sprintf("%.2f",12.234324)
> cat(a,sep="\n")
> #+END_SRC
>
> #+RESULTS:
> : 12.23
>
> This is with
>
> GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 2.24.32) of
> 2019-05-01
> Org mode version 9.2.3 (release_9.2.3-367-gd79e80 @
> /home/nick/elisp/org-mode/lisp/)
> R version 3.5.3 (2019-03-11) -- "Great Truth"
>
> on Fedora 29.
>
I get what Jeremie reports (but he has a blank line inserted after the first
line, IIUC)
This is with:
GNU Emacs 26.1
Org 9.2.3
ess-version: 18.10.3
R version 3.6.0 (2019-04-26)
I believe this is new-ish behavior. I see some older files without the extra
line. Also, I think there are recent changes in ESS that pertain to comint
sessions.
FWIW, here is a clip from my session:
--8<---cut here---start->8---
> x <- 6L
a <-sprintf("%.2f",12.234324)
cat(a,sep="\n")
'org_babel_R_eoe'
> >
12.23
>
[1] "org_babel_R_eoe"
--8<---cut here---end--->8---
If Nick sees something different maybe a change in ESS is the culprit.
Not sure what the right path forward is ob-R.el, but as a workaround the OP can
use a :post header arg to strip the offending line.
HTH,
Chuck
Re: [O] Problems with inline source blocks
> On May 27, 2019, at 9:47 AM, Christian Heinrich
> wrote:
>
> Hi everyone,
>
> several issues with inline source blocks:
None of the behavior you cite is in the current master as of 28-may-2019:
4a383ee0f19a001b272097398b43312fc0655798
>
> 1) https://orgmode.org/manual/Exporting-code-blocks.html states:
>
>> The :exports header arguments control exporting code blocks only and
>> not inline code:
No mention of inline blocks in 14.6 Exporting Code Blocks. I guess that web
page needs to update or refers to something other than master.
>
> but
> https://orgmode.org/manual/Using-Header-Arguments.html#Using-Header-Arguments
> gives as example:
>
>> src_haskell[:exports both]{fac 5}
>
> Which one is true?
>
As you can verify with your test, header args do affect inline src blocks. I
believe this is consistent with the current manual.
> 2) I cannot get the results of inline blocks to be exported.
>
> When I have a file that contains:
>
>> Test: src_R[:exports results]{4*4} {{{results(=16=)}}}
This worked for me when exporting to an ascii buffer.
There were some problems starting with
5f5d82ed516b7b385a9258271becbfa247e94af3, but these were fixed long ago.
>
> then the code is always exported but the results are only exported up to
> 623cc4625950f84442d4cde0faa9cc3ea0233283
>
> but starting from 65ebb128bc380fe4795dedd655d6f7b685249842
> the results macro is ignored and the result never appears.
>
> Looking at online documentation (other projects) like
> https://org-babel.readthedocs.io/en/latest/eval/#inline-code-blocks I realize
> that this may be a
> problem in general (look at the Example sections, such as "The answer to 2 +
> 3 is .")
>
>
> 3) The source block never gets evaluated. I tried
> src_sh{touch /tmp/test21.txt}
> but this file doesn't get created, only when I execute it directly.
I ran this and it produced the file:
src_sh{touch ~/test21.txt;echo "done"}
Without the echo, export fails as touch produces no result.
>
> Can anyone point out what I'm doing wrong, or is this actually a bug? I can't
> even get a basic
> source block like
>
> #+begin_src R :results output :session *R* :exports none
> 5*5
> #+end_src
>
> to ignore the code when exporting (but it's not evaluated).
>
In my test, the code is evaluated in the session, but no results are reported.
>
> Thanks!
> Christian
If I had to guess, I'd say there is something wrong with your installation.
If you think otherwise, an ECM that runs with only a minimal init file (that
you specify) might be helpful.
HTH,
Chuck
Re: [O] Advance notice of birthdays in org-mode via org-contacts
Alan Schmitt writes: > Hi Eric, > > On 2019-05-28 04:34, Eric Abrahamsen writes: > >> And (shameless plug) if you're using EBDB, you can set both >> `ebdb-use-diary' and `org-agenda-include-diary' to t, and >> anniversaries >> will show in the agenda. > > Thank you for the plug, I've been wanting to look at EBDB for a while. > I > have a few questions: is it easy to migrate data from BBDB? Can you > have > org links to EBDB records? Does it work with mu4e for address > completion? Glad you're considering it! EBDB will migrate automatically from versions 2 or 3 of BBDB (it is slow, but you only have to do it once), you just have to have the `bbdb-file' variable pointing to a valid BBDB file, then call `ebdb-open'. It supports org links, either to single records, or to record searches: following a link like "ebdb:mail/@gnu.org" will search for all records with Gnu email addresses. You can also tag your records with org tags, and pop up an EBDB window alongside a tag agenda search, for instance. In theory it supports mu4e, but I think you would be the first user, if you tried it, so beware! :) Eric
Re: [O] Temporarily setting agenda files list, cleaning up
Many thanks to John and Thomas for their suggestions! Thomas Plass wrote: > This will use a private set of 'org-agenda-files and kill their > buffers after executing `org-agenda-list': > > (...) This function is a very good prototype of what I had in mind. The details like it closing buffers that were already open before do not matter for now. (John's post offers a solution to this particular problem.) I replaced the call to org-agenda-list with one to org-agenda, in order to get the full thing, and this works. The prototype reveals a problem with the approach: if the buffers with the agenda files are closed immediately (to avoid cluttering the buffer list with possibly hundreds of buffers), most of the agenda functionality no longer works. It's not possible to jump to entries, reschedule them, etc. I guess that modifying orgmode so that agenda buffers open files as needed would by rather complicated. The simpler alternative should be to keep the buffers open and only kill them when the associated agenda buffer itself gets killed. I suppose that this can be done by using kill-buffer-hook. It seems that the buffer killing can be made smarter by storing the buffer-modified-tick at the time of the agenda construction for all the buffers that are to be closed. This information can then be used later to only kill buffers that haven't been touched since. Ideally, one should also check whether it is still the *same* buffer, because it might have been closed and reopened on purpose by the user. (I have no good idea how to check for that, other than storing opening times of org buffers using some hook and using that.) By the way, the function directory-files-recursively takes 1.5 s to search my (huge) work directory for org files. Using shell-command-to-string to launch the 'find' shell command takes only 0.2 s. Christoph signature.asc Description: PGP signature
[O] [PATCH] org-clock.el: Fix restore of frame-title-format
* lisp/org-clock.el (org-frame-title-format-backup): Use nil as initial value. (org-clock-in): set `org-frame-title-format-backup' to `frame-title-format'. (org-clock-restore-frame-title-format): New function. (org-clock-out): Use it. (org-clock-cancel): Use it. The problem was that the `org-frame-title-format-backup' variable is initialized on org-clock.el loading and future changes to `frame-title-format' is ignored. TINYCHANGE --- lisp/org-clock.el | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/lisp/org-clock.el b/lisp/org-clock.el index 9a8928a49..12b412f7b 100644 --- a/lisp/org-clock.el +++ b/lisp/org-clock.el @@ -41,7 +41,7 @@ (declare-function org-table-goto-line "org-table" (n)) (declare-function org-dynamic-block-define "org" (type func)) -(defvar org-frame-title-format-backup frame-title-format) +(defvar org-frame-title-format-backup nil) (defvar org-state) (defvar org-link-bracket-re) (defvar org-time-stamp-formats) @@ -1359,6 +1359,7 @@ the default behavior." ;; add to frame title (when (or (eq org-clock-clocked-in-display 'frame-title) (eq org-clock-clocked-in-display 'both)) + (setq org-frame-title-format-backup frame-title-format) (setq frame-title-format org-clock-frame-title-format)) (org-clock-update-mode-line) (when org-clock-mode-line-timer @@ -1549,6 +1550,14 @@ line and position cursor in that line." (org-log-states-order-reversed (goto-char (car (last positions (t (goto-char (car positions +(defun org-clock-restore-frame-title-format () + "Restore `frame-title-format' from `org-frame-title-format-backup'. +`frame-title-format' is restored if `org-frame-title-format-backup' is not nil +and current `frame-title-format' is equal to `org-clock-frame-title-format'." + (when (and org-frame-title-format-backup +(equal frame-title-format org-clock-frame-title-format)) +(setq frame-title-format org-frame-title-format-backup))) + ;;;###autoload (defun org-clock-out ( switch-to-state fail-quietly at-time) "Stop the currently running clock. @@ -1560,7 +1569,7 @@ to, overriding the existing value of `org-clock-out-switch-to-state'." (when (not (org-clocking-p)) (setq global-mode-string (delq 'org-mode-line-string global-mode-string)) - (setq frame-title-format org-frame-title-format-backup) + (org-clock-restore-frame-title-format) (force-mode-line-update) (if fail-quietly (throw 'exit t) (user-error "No active clock"))) (let ((org-clock-out-switch-to-state @@ -1618,7 +1627,7 @@ to, overriding the existing value of `org-clock-out-switch-to-state'." (setq org-clock-idle-timer nil)) (setq global-mode-string (delq 'org-mode-line-string global-mode-string)) - (setq frame-title-format org-frame-title-format-backup) + (org-clock-restore-frame-title-format) (when org-clock-out-switch-to-state (save-excursion (org-back-to-heading t) @@ -1718,7 +1727,7 @@ Optional argument N tells to change by that many units." (when (not (org-clocking-p)) (setq global-mode-string (delq 'org-mode-line-string global-mode-string)) -(setq frame-title-format org-frame-title-format-backup) +(org-clock-restore-frame-title-format) (force-mode-line-update) (error "No active clock")) (save-excursion; Do not replace this with `with-current-buffer'. @@ -1734,7 +1743,7 @@ Optional argument N tells to change by that many units." (move-marker org-clock-hd-marker nil) (setq global-mode-string (delq 'org-mode-line-string global-mode-string)) - (setq frame-title-format org-frame-title-format-backup) + (org-clock-restore-frame-title-format) (force-mode-line-update) (message "Clock canceled") (run-hooks 'org-clock-cancel-hook)) -- 2.15.1
Re: [O] manual errata
Hi Nicholas, it is shown on this page. Is there a more up to date version of the manual I should reference? https://orgmode.org/manual/Inserting-deadline_002fschedule.html#Inserting-deadline_002fschedule Best, Ian On Tue, May 28, 2019 at 5:00 AM Nicolas Goaziou wrote: > Hello, > > Ian Garmaise writes: > > > org 9.2 pdf manual > > > > In Chapter 8, p. 78 > > > > function org-mark-entry-for-agenda action > > C-c C-x C-k > > > > This function doesn't exist in my version of org-mode (9.2.3) > > I cannot find any reference to this function in current manual. > > Regards, > > -- > Nicolas Goaziou > -- = Ian Garmaise Consultant Phorix Solutions Group ia...@phorixsol.com Toronto cell: 416.432.2251 NYC: 917.512.9535 https://www.linkedin.com/in/igarmaise/ http://www.PhorixSol.com
[O] Bug: agenda-tag-filter-preset not working, when ":newline" inside a tag radiogroup [9.2.3 (9.2.3-20-g31873e-elpaplus @ /home/msm/.emacs.d/elpa/org-plus-contrib-20190527/)]
--text follows this line--
I use the org-agenda-tag-filter-preset in my custom agenda
commands.
This breaks, when there is a (:newline) inside a radiogroup in
org-tag-alist. When calling the agenda command, it gives the error:
"mapcar: Wrong type argument: char-or-string-p, :newline"
and the agenda gets built without the filter-preset.
The minimal configuration (via customize-interface) below, shows the state
triggering the error. Remove the (:newline) from inside the radiogroup in
org-tag-alist and the filter-preset works again.
Please fix it, so the filter-presets can be used together with
(:newline) in tag-radiogroups.
Questions anytime..
Thanks for your effort and great piece of software!
-Jens
Emacs : GNU Emacs 26.2 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
of 2019-04-12
Package: Org mode version 9.2.3 (9.2.3-20-g31873e-elpaplus @
/home/msm/.emacs.d/elpa/org-plus-contrib-20190527/)
current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-agenda-files '("~/org-test.org")
org-tag-alist '((:startgroup) ("domain" . 32) (:grouptags) ("work" . 119)
(:newline) ("private" . 112)
(:endgroup) (:newline) ("other" . 32))
org-mode-hook '(#[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-eldoc-load)
org-archive-hook '(org-attach-archive-delete-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
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-babel-pre-tangle-hook '(save-buffer)
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
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-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 org-rmail-store-link)
("mhe" :follow org-mhe-open :store org-mhe-store-link)
("irc" :follow org-irc-visit :store org-irc-store-link :export
org-irc-export)
("info" :follow org-info-open :export org-info-export :store
org-info-store-link)
("gnus" :follow org-gnus-open :store org-gnus-store-link)
("docview" :follow org-docview-open :export org-docview-export :store
org-docview-store-link)
("bibtex" :follow org-bibtex-open :store org-bibtex-store-link)
("bbdb" :follow org-bbdb-open :export org-bbdb-export :complete
org-bbdb-complete-link
:store org-bbdb-store-link)
("w3m" :store org-w3m-store-link) ("file+sys") ("file+emacs")
("doi" :follow org--open-doi-link) ("elisp" :follow
org--open-elisp-link)
("file" :complete org-file-complete-link)
("ftp" :follow (lambda (path) (browse-url (concat "ftp:" path
("help" :follow org--open-help-link)
("http" :follow (lambda (path) (browse-url (concat "http:" path
("https" :follow (lambda (path) (browse-url (concat "https:" path
("mailto" :follow (lambda (path) (browse-url (concat "mailto:;
path
("news" :follow (lambda (path) (browse-url (concat "news:; path
("shell" :follow org--open-shell-link))
org-agenda-custom-commands '(("n" "Agenda and all TODOs" ((agenda "" nil)
(alltodo "" nil))
((org-agenda-tag-filter-preset (quote ("-work")
)
)
Re: [O] [PATCH] Docstring update
Hello, "Cheong Yiu Fung" writes: > Fix docstring of `org-latex-packages-alist'. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] org-clock-out overrides frame-title-format [9.2.3 (9.2.3-17-g4df705-elpa @ ~/.emacs.d/elpa/org-20190513/)]
Hello, Andrii Kolomoiets writes: > The org-frame-title-format-backup variable is initialized on > org-clock.el loading and future changes to frame-title-format is > ignored: > > 1. emacs -Q > 2. M-: frame-title-format >It's "%b" > 3. M-: (require 'org-clock) > 4. (setq frame-title-format "%b bar") > 5. C-x b test.org > 6. M-x org-mode > 7. Insert heading (M-RET foo) > 8. M-x org-clock-in > 9. M-x org-clock-out > 10. M-: frame-title-format > It's "%b" again > > With provided patch org-frame-title-format-backup is initialized on > org-clock-in. Also frame-title-format is restored to > org-frame-title-format-backup only if current frame-title-format is > equal to org-clock-frame-title-format in case frame title format is > changed after org-clock-in. Thank you. I think this could be factored out a bit, for example creating a simple function taking care of updating `frame-title-format' if needed. Also, could you provide a proper commit message and use git format-patch to send it again? Regards, -- Nicolas Goaziou
Re: [O] manual errata
Hello, Ian Garmaise writes: > org 9.2 pdf manual > > In Chapter 8, p. 78 > > function org-mark-entry-for-agenda action > C-c C-x C-k > > This function doesn't exist in my version of org-mode (9.2.3) I cannot find any reference to this function in current manual. Regards, -- Nicolas Goaziou
Re: [O] Advance notice of birthdays in org-mode via org-contacts
Hi Eric, On 2019-05-28 04:34, Eric Abrahamsen writes: And (shameless plug) if you're using EBDB, you can set both `ebdb-use-diary' and `org-agenda-include-diary' to t, and anniversaries will show in the agenda. Thank you for the plug, I've been wanting to look at EBDB for a while. I have a few questions: is it easy to migrate data from BBDB? Can you have org links to EBDB records? Does it work with mu4e for address completion? Thanks, Alan signature.asc Description: PGP signature
