Re: [O] How to include diary anniversary entries into default org-agenda?
Sorry, that's my mis-type. You example works. Now the problem is: > #+begin_src org > ,* Anniversary > > ,** my first child anniversary > > %%(diary-anniversary 10 26 2017) > > ,** Funeral Arrangement > > ,*** kk > > %%(diary-anniversary 12 8 2007) > #+end_src Then org-agenda shows all headlines which has anniversary entry. Like: - Valentine's Day - My Birthday - my first child anniversary Without considering whether the anniversary date is a day past one year? (I think anniversary is by default repeat one year. Like org-mode timestamp repeat. <2017-12-21 Thu +1y>) I know there are other diary anniversary syntax like: - ~%%(diary-anniversary 3 24 2014)~ diary anniversary - ~%%(diary-cyclic 2 7 26 2014)~ repeated diary. - ~%%(diary-block 7 26 2014 8 26 2020)~ diary block - ~%%(diary-float t 5 1)~ happens every 1st Friday of the month. I checked out those syntax in Org-mode Info diary nod. This seems a little kind of off my original topic. On 12/21/2017 03:42 PM, Nick Dokos wrote: "numbch...@gmail.com" writes: I tried %%(org-anniversary 2016 12 21) Test anniversary. But this seems does not work. I tested with variable diary-file default value point to ~/.emacs.d/diary file. and has following content: ... %%(org-anniversary 2016 12 21) Test anniversary Works fine here. Where are you adding this line? You have to put this in an agenda file, otherwise it will not be processed.
Re: [O] How to include diary anniversary entries into default org-agenda?
"numbch...@gmail.com" writes: > I tried %%(org-anniversary 2016 12 21) Test anniversary. But this > seems does not work. I tested with variable diary-file default value > point to ~/.emacs.d/diary file. and has following content: > > ... > > %%(org-anniversary 2016 12 21) Test anniversary > Works fine here. Where are you adding this line? You have to put this in an agenda file, otherwise it will not be processed. -- Nick
Re: [O] Git repository error
> Robert Klein writes: > Hi guys, I removed old git-daemon processes and restartet the git > daemon. > Does it work better, now? Yes, it does. I have just updated successfully with an old school 'git pull'. Thanks. -- Colin Baxter m43...@yandex.com - GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8 - Since mathematicians have invaded the theory of relativity, I do not understand it myself. A. Einstein
[O] Bug: Tangling python code results in mixed tabs and spaces, incomaptible with python3 [9.1.4 (9.1.4-dist @ /home/ehere/emacs-scripts/org-9.1.4/lisp/)]
The following python code uses only whitespaces for the different indentdation levels: a_list = ['elem1', 'elem2', 'elem3'] for elem in a_list: print(elem) for char in elem: print char I enter this code into a SRC block with #+BEGIN_SRC python :tangle blank_test.py #+END_SRC by pressing C-' inside the block (which opens the editing buffer python-mode). Then I press C-' again, after which I tangle the code to blank_test.py by pressing C-u C-c C-v C-t. The resulting file blank_test.py will contain a mix of tabs and spaces for the different intendation levels. (I checked this with whitespace.el). Above behaviour is a bug, since Python3 forbids mixing of spaces and tabs. (Python2 is more relaxed about mixing of tabs and spaces). Thus, the above code, syntactical correctly entered into an OrgSrc buffer, will result in code that can not be run in python3 when tangled from an org-mode file. Emacs : GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 2017-09-12 on hullmann, modified by Debian Package: Org mode version 9.1.4 (9.1.4-dist @ /home/ehere/emacs-scripts/org-9.1.4/lisp/)
Re: [O] How to include diary anniversary entries into default org-agenda?
stardiviner writes: > I have an org-mode file: > > #+begin_src org > ,* Anniversary > > ,** my first child anniversary > > %%(diary-anniversary 10 26 2017) > > ,** Funeral Arrangement > > ,*** kk > > %%(diary-anniversary 12 8 2007) > #+end_src > > How to include and show them in default org-agenda day view by > configuring org-mode? Try org-anniversary. The line %%(org-anniversary 2016 12 20) Test anniversary Generates an anniversary in the agenda. In the default daily agenda it is mixed in with the tasks and deadlines, so it may be easy to miss. Note the order of the date elements is year, month, day and all three are needed. There is an option final element of type MARK what could be used to adjust fonts and the like. R Horn
Re: [O] Git repository error
Hi guys, I removed old git-daemon processes and restartet the git daemon. Does it work better, now? Best regards Robert On Wed, 20 Dec 2017 18:03:01 + li...@wilkesley.net wrote: > On 2017-12-20 17:14, swfl...@flintfam.org wrote: > > > I'm still having this problem > > > > CB> -- Colin Baxter m43...@yandex.com > > CB> > > - > > CB> GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 > > CB> 91F5 41C8 > > CB> > > - > > CB> The sole cause of all human misery is the inability of > > CB> people > > to > > CB> sit quietly in their rooms. Blaise Pascal, 1670 > > Same here: > > dell src/org-mode ‹master› » git pull > -v > 1 ↵ > Looking up orgmode.org ... done. > Connecting to orgmode.org (port 9418) ... 104.239.132.130 done. > fatal: read error: Connection reset by peer > > > Ian. >
Re: [O] How to include diary anniversary entries into default org-agenda?
Sorry. I try to edit it in Emacs. but it is messed up by Gmail format. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Thu, Dec 21, 2017 at 10:40 AM, numbch...@gmail.com wrote: > Sorry > > [stardiviner] GPG key ID: 47C32433 > IRC(freeenode): stardiviner Twitter: @numbchild > Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 > Blog: http://stardiviner.github.io/ > > On Thu, Dec 21, 2017 at 10:40 AM, numbch...@gmail.com > wrote: > >> I tried %%(org-anniversary 2016 12 21) Test anniversary. But this seems >> does not work. I tested with variable diary-file default value point to >> ~/.emacs.d/diary file. and has following content: >> >> %%(diary-anniversary 10 21 2016) my first child >> <%%(diary-anniversary 10 21 2016)> my first child >> %%(org-anniversary 2016 12 21) Test anniversary >> >> >> Then I try to change diary file to an org-mode file. Has following >> content: >> >> * Holiday >> >> %%(org-calendar-holiday) >> >> ** Valentine's Day >> >> <%%(diary-anniversary 2 14 2017)> >> >> >> * Birthday >> >> ** My Birthday >> >> <%%(diary-anniversary 3 24 1990)> I'm %d%s years old today!!! >> >> * Anniversary >> >> ** my first child anniversary >> >> <%%(diary-anniversary 10 26 2017)> >> >> >> >> Then org-agenda shows all headlines which has anniversary entry. Like: - >> Valentine's Day - My Birthday - my first child anniversary Without >> considering whether the anniversary date is a day past one year? (I think >> anniversary is by default repeat one year. Like org-mode timestamp repeat. >> <2017-12-21 Thu +1y>) I know there are other diary anniversary syntax like: >> - ~%%(diary-anniversary 3 24 2014)~ diary anniversary - ~%%(diary-cyclic 2 >> 7 26 2014)~ repeated diary. - ~%%(diary-block 7 26 2014 8 26 2020)~ diary >> block - ~%%(diary-float t 5 1)~ happens every 1st Friday of the month. I >> checked out them in Org-mode Info diary node. >> >> [stardiviner] GPG key ID: 47C32433 >> IRC(freeenode): stardiviner Twitter: @numbchild >> Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 >> Blog: http://stardiviner.github.io/ >> >> On Wed, Dec 20, 2017 at 11:40 PM, Robert Horn >> wrote: >> >>> >>> stardiviner writes: >>> >>> > I have an org-mode file: >>> > >>> > #+begin_src org >>> > ,* Anniversary >>> > >>> > ,** my first child anniversary >>> > >>> > %%(diary-anniversary 10 26 2017) >>> > >>> > ,** Funeral Arrangement >>> > >>> > ,*** kk >>> > >>> > %%(diary-anniversary 12 8 2007) >>> > #+end_src >>> > >>> > How to include and show them in default org-agenda day view by >>> > configuring org-mode? >>> >>> Try org-anniversary. The line >>> >>> %%(org-anniversary 2016 12 20) Test anniversary >>> >>> Generates an anniversary in the agenda. In the default daily agenda it >>> is mixed in with the tasks and deadlines, so it may be easy to miss. >>> >>> Note the order of the date elements is year, month, day and all three >>> are needed. There is an option final element of type MARK what could be >>> used to adjust fonts and the like. >>> >>> R Horn >>> >> >> >
Re: [O] How to include diary anniversary entries into default org-agenda?
Sorry [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Thu, Dec 21, 2017 at 10:40 AM, numbch...@gmail.com wrote: > I tried %%(org-anniversary 2016 12 21) Test anniversary. But this seems > does not work. I tested with variable diary-file default value point to > ~/.emacs.d/diary file. and has following content: > > %%(diary-anniversary 10 21 2016) my first child > <%%(diary-anniversary 10 21 2016)> my first child > %%(org-anniversary 2016 12 21) Test anniversary > > > Then I try to change diary file to an org-mode file. Has following > content: > > * Holiday > > %%(org-calendar-holiday) > > ** Valentine's Day > > <%%(diary-anniversary 2 14 2017)> > > > * Birthday > > ** My Birthday > > <%%(diary-anniversary 3 24 1990)> I'm %d%s years old today!!! > > * Anniversary > > ** my first child anniversary > > <%%(diary-anniversary 10 26 2017)> > > > > Then org-agenda shows all headlines which has anniversary entry. Like: - > Valentine's Day - My Birthday - my first child anniversary Without > considering whether the anniversary date is a day past one year? (I think > anniversary is by default repeat one year. Like org-mode timestamp repeat. > <2017-12-21 Thu +1y>) I know there are other diary anniversary syntax like: > - ~%%(diary-anniversary 3 24 2014)~ diary anniversary - ~%%(diary-cyclic 2 > 7 26 2014)~ repeated diary. - ~%%(diary-block 7 26 2014 8 26 2020)~ diary > block - ~%%(diary-float t 5 1)~ happens every 1st Friday of the month. I > checked out them in Org-mode Info diary node. > > [stardiviner] GPG key ID: 47C32433 > IRC(freeenode): stardiviner Twitter: @numbchild > Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 > Blog: http://stardiviner.github.io/ > > On Wed, Dec 20, 2017 at 11:40 PM, Robert Horn wrote: > >> >> stardiviner writes: >> >> > I have an org-mode file: >> > >> > #+begin_src org >> > ,* Anniversary >> > >> > ,** my first child anniversary >> > >> > %%(diary-anniversary 10 26 2017) >> > >> > ,** Funeral Arrangement >> > >> > ,*** kk >> > >> > %%(diary-anniversary 12 8 2007) >> > #+end_src >> > >> > How to include and show them in default org-agenda day view by >> > configuring org-mode? >> >> Try org-anniversary. The line >> >> %%(org-anniversary 2016 12 20) Test anniversary >> >> Generates an anniversary in the agenda. In the default daily agenda it >> is mixed in with the tasks and deadlines, so it may be easy to miss. >> >> Note the order of the date elements is year, month, day and all three >> are needed. There is an option final element of type MARK what could be >> used to adjust fonts and the like. >> >> R Horn >> > >
Re: [O] How to include diary anniversary entries into default org-agenda?
I tried %%(org-anniversary 2016 12 21) Test anniversary. But this seems does not work. I tested with variable diary-file default value point to ~/.emacs.d/diary file. and has following content: %%(diary-anniversary 10 21 2016) my first child <%%(diary-anniversary 10 21 2016)> my first child %%(org-anniversary 2016 12 21) Test anniversary Then I try to change diary file to an org-mode file. Has following content: * Holiday %%(org-calendar-holiday) ** Valentine's Day <%%(diary-anniversary 2 14 2017)> * Birthday ** My Birthday <%%(diary-anniversary 3 24 1990)> I'm %d%s years old today!!! * Anniversary ** my first child anniversary <%%(diary-anniversary 10 26 2017)> Then org-agenda shows all headlines which has anniversary entry. Like: - Valentine's Day - My Birthday - my first child anniversary Without considering whether the anniversary date is a day past one year? (I think anniversary is by default repeat one year. Like org-mode timestamp repeat. <2017-12-21 Thu +1y>) I know there are other diary anniversary syntax like: - ~%%(diary-anniversary 3 24 2014)~ diary anniversary - ~%%(diary-cyclic 2 7 26 2014)~ repeated diary. - ~%%(diary-block 7 26 2014 8 26 2020)~ diary block - ~%%(diary-float t 5 1)~ happens every 1st Friday of the month. I checked out them in Org-mode Info diary node. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Wed, Dec 20, 2017 at 11:40 PM, Robert Horn wrote: > > stardiviner writes: > > > I have an org-mode file: > > > > #+begin_src org > > ,* Anniversary > > > > ,** my first child anniversary > > > > %%(diary-anniversary 10 26 2017) > > > > ,** Funeral Arrangement > > > > ,*** kk > > > > %%(diary-anniversary 12 8 2007) > > #+end_src > > > > How to include and show them in default org-agenda day view by > > configuring org-mode? > > Try org-anniversary. The line > > %%(org-anniversary 2016 12 20) Test anniversary > > Generates an anniversary in the agenda. In the default daily agenda it > is mixed in with the tasks and deadlines, so it may be easy to miss. > > Note the order of the date elements is year, month, day and all three > are needed. There is an option final element of type MARK what could be > used to adjust fonts and the like. > > R Horn >
Re: [O] Canonical way to strip off all markup from an element in Org exporter backend?
On Wed, Dec 20, 2017 at 5:27 PM Nicolas Goaziou wrote: > You must be kidding. It must be around 8 locs. See for example > `org-export-toc-entry-backend'. > Thank you! That function is educational. I'll play more with that idea. It will be a lot more verbose than the 3 line solution I have right now.. but I am intrigued enough to still try that out to see how it turns out. I fail to see how it could be generally useful. > It can be used wherever just the element content is needed without formatting properties, like in my case where the element title is needed to be extracted without any formatting. > What are you doing with entities, footnotes, latex-snippets...? > I haven't yet invested any time into serious development of this "base class" backend. The idea of this exporter is to give formatting-free output (like when you select plain text option in an email client).. so at whim, entities will be translated to the correct unicode chars, footnotes behavior could be the same as ox-ascii, and latex-snippets can stay in the raw ascii form. If there is an interest to move this forward, I can come up with a "raw" backend spec, and we can discuss on the details. -- Kaushal Modi
[O] TIL about use of eval in user Org macros.. Documentation?
Hello, The commit message in this commit is golden: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=3ac619c8ac9934a2a1368f3de8ffad951f900067 Using that info, I came up with a "classified" version of n macro for markdown/HTML: #+MACRO: sec (eval (concat "" (number-to-string (org-macro--counter-increment $1 $2)) "")) Based on that I have two questions: 1. Can you please document the use of eval form in Org macro definitions in the Org manual(.org)? Its awesome wasn't evident to me until I read that commit message. 2. (Another question on canonical approach) What would be the recommended approach for an exporter backend to add new macros or override existing macros (like "n" macro to wrap the string with HTML class as an example)? Should it update org-macro-templates in org-export-before-processing-hook? or something similar? -- Kaushal Modi
Re: [O] Canonical way to strip off all markup from an element in Org exporter backend?
Kaushal Modi writes: > Thanks! I feared so. Then the strip-HTML-tags approach seems to be the > quickest. You must be kidding. It must be around 8 locs. See for example `org-export-toc-entry-backend'. > Would there be an interest to add that to the core something like a "base > class" of exporter backends? I fail to see how it could be generally useful. > "strip off all markup" simply means export something like "*abc* /def/ > =ghi= ~jkl~ +mno+ _pqr_" as "abc def ghi jkl mno pqr". Think of that as a > backend without even the minimal adornment that ox-ascii has... and > ox-ascii can be a derived backend from this one. What are you doing with entities, footnotes, latex-snippets...?
Re: [O] [PATCH] Fix for double-escaping # and ![ in ox-md
On Wed, Dec 20, 2017 at 5:07 PM Nicolas Goaziou wrote: > > If this looks good, I can commit this to maint. > > It looks good. Thank you. > Thanks. It's now committed to maint and merged to master. -- Kaushal Modi
Re: [O] Canonical way to strip off all markup from an element in Org exporter backend?
On Wed, Dec 20, 2017 at 5:04 PM Nicolas Goaziou wrote: > You could write a dedicated (anonymous) back-end for that, Thanks! I feared so. Then the strip-HTML-tags approach seems to be the quickest. > if you have a clear idea about what "strip off all markup" means. > Would there be an interest to add that to the core something like a "base class" of exporter backends? "strip off all markup" simply means export something like "*abc* /def/ =ghi= ~jkl~ +mno+ _pqr_" as "abc def ghi jkl mno pqr". Think of that as a backend without even the minimal adornment that ox-ascii has... and ox-ascii can be a derived backend from this one. -- Kaushal Modi
Re: [O] [PATCH] Fix for double-escaping # and ![ in ox-md
Hello, Kaushal Modi writes: > Note that the # and ![ are double-escaped. So any markdown->HTML renderer > will print that "\" as it is. > > Digging through ox-md.el, I found that the order of > replace-regexp-in-string was incorrect in org-md-plain-text. > > Here's the diff: > > = > diff --git a/lisp/ox-md.el b/lisp/ox-md.el > index 12188387355..927a73b780c 100644 > --- a/lisp/ox-md.el > +++ b/lisp/ox-md.el > @@ -500,14 +500,15 @@ TEXT is the string to transcode. INFO is a plist > holding > contextual information." >(when (plist-get info :with-smart-quotes) > (setq text (org-export-activate-smart-quotes text :html info))) > + ;; The below series of replacements in `text' is order sensitive. > + ;; Protect `, *, _, and \ > + (setq text (replace-regexp-in-string "[`*_\\]" "\\&" text)) >;; Protect ambiguous #. This will protect # at the beginning of >;; a line, but not at the beginning of a paragraph. See >;; `org-md-paragraph'. >(setq text (replace-regexp-in-string "\n#" "\n#" text)) >;; Protect ambiguous ! >(setq text (replace-regexp-in-string "\\(!\\)\\[" "!" text nil nil > 1)) > - ;; Protect `, *, _ and \ > - (setq text (replace-regexp-in-string "[`*_\\]" "\\&" text)) >;; Handle special strings, if required. >(when (plist-get info :with-special-strings) > (setq text (org-html-convert-special-strings text))) > = > > After applying this patch, the same portion exported doesn't have > double-escaping before # and ![. > > If this looks good, I can commit this to maint. It looks good. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Canonical way to strip off all markup from an element in Org exporter backend?
Hello, Kaushal Modi writes: > What's the canonical way to strip off all markup from an element in an Org > exporter backend. You could write a dedicated (anonymous) back-end for that, if you have a clear idea about what "strip off all markup" means. Regards, -- Nicolas Goaziou
[O] Canonical way to strip off all markup from an element in Org exporter backend?
Hello, What's the canonical way to strip off all markup from an element in an Org exporter backend. I do it in this round-about way in ox-hugo..it works but feels convoluted. The trick is to remove all markup chars from an element while retaining the *, /, `, etc chars *not* used for any markup. I export Org subtrees to individual posts, where the subtree headline will become the post title. So I need to sanitize that headline of any markup. Step1: I get the HTMLized version of the title (org-export-data-with-backend (plist-get info :title) 'html info) But getting the HTMLized version of the title, it would be easy to strip off the HTML tags which would be inserted basically for formatting (bold, italics, etc.). Step 2: Strip off the HTML tags. (while (string-match "<\\(?1:[a-z]+\\)[^>]*>\\(?2:[^<]+\\)" title) (setq title (replace-match "\\2" nil nil title))) If I do any other exporter like md, I will lose the ability to distinguish a literal * in the title from a * meant for bold/italics markup in Markdown. Even ascii is not good because then I'd need to do some intensive parsing to figure out if ` is meant to be a literal ` or part of `code'. So the question: Is this the best way.. or is there a canonical way to export an element without any markup char? Full actual code[1]. [1]: https://github.com/kaushalmodi/ox-hugo/blob/dffb7e970f33959a0b97fb8df267a54d01a98a2a/ox-hugo.el#L1769-L1802 -- Kaushal Modi
[O] [PATCH] Fix for double-escaping # and ![ in ox-md
Hello, I have this test case; export it by doing C-c C-e C-s m M (assuming ox-md is required.. I think it is required by default). = * Escaping hashes and exclamations correctly in body :PROPERTIES: :EXPORT_FILE_NAME: escaping-hashes-and-exclamations-in-body :END: I intend to show these # characters verbatim; they should not render as Markdown headings. They also shouldn't show up with a leading =\= in the final rendered output. # This is an Org comment #This is not an Org comment. It has a hash char at beginning of a paragraph which must be escaped just once i.e. show up as =\#= in Markdown. blah # This isn't an Org comment either This * will be escaped just once i.e. show up as =\*= in Markdown. This _ will be escaped just once i.e. show up as =\_= in Markdown. This \ will be escaped just once i.e. show up as =\\= in Markdown. Hash char at beginning of a continued line #like this must be escaped just once i.e. show up as =\#= in Markdown. ![this exclamation must be escaped just once i.e. show up as =\!= in Markdown] This ! does not need to be escaped as there is no ambiguity. = Here's the relevant excerpt of the export that is erroneous: = Hash char at beginning of a continued line \\#like this must be escaped just once i.e. show up as `\#` in Markdown. \\![this exclamation must be escaped just once i.e. show up as `\!` in Markdown] = Note that the # and ![ are double-escaped. So any markdown->HTML renderer will print that "\" as it is. Digging through ox-md.el, I found that the order of replace-regexp-in-string was incorrect in org-md-plain-text. Here's the diff: = diff --git a/lisp/ox-md.el b/lisp/ox-md.el index 12188387355..927a73b780c 100644 --- a/lisp/ox-md.el +++ b/lisp/ox-md.el @@ -500,14 +500,15 @@ TEXT is the string to transcode. INFO is a plist holding contextual information." (when (plist-get info :with-smart-quotes) (setq text (org-export-activate-smart-quotes text :html info))) + ;; The below series of replacements in `text' is order sensitive. + ;; Protect `, *, _, and \ + (setq text (replace-regexp-in-string "[`*_\\]" "\\&" text)) ;; Protect ambiguous #. This will protect # at the beginning of ;; a line, but not at the beginning of a paragraph. See ;; `org-md-paragraph'. (setq text (replace-regexp-in-string "\n#" "\n#" text)) ;; Protect ambiguous ! (setq text (replace-regexp-in-string "\\(!\\)\\[" "!" text nil nil 1)) - ;; Protect `, *, _ and \ - (setq text (replace-regexp-in-string "[`*_\\]" "\\&" text)) ;; Handle special strings, if required. (when (plist-get info :with-special-strings) (setq text (org-html-convert-special-strings text))) = After applying this patch, the same portion exported doesn't have double-escaping before # and ![. If this looks good, I can commit this to maint. -- Kaushal Modi
Re: [O] Git repository error
On 2017-12-20 17:14, swfl...@flintfam.org wrote: I'm still having this problem CB> -- Colin Baxter m43...@yandex.com CB> - CB> GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 CB> 41C8 CB> - CB> The sole cause of all human misery is the inability of people to CB> sit quietly in their rooms. Blaise Pascal, 1670 Same here: dell src/org-mode ‹master› » git pull -v 1 ↵ Looking up orgmode.org ... done. Connecting to orgmode.org (port 9418) ... 104.239.132.130 done. fatal: read error: Connection reset by peer Ian.
Re: [O] Git repository error
> Colin Baxter writes: > Marco Wahl writes: >> Jack Kamm writes: >>> I'm having the same issue as Josiah, are others able to pull >>> from the git repo? >> git pull works for me. >> Maybe the following questions lead to a better understanding. >> What about performing a plain >> git pull >> instead of make update? >> What about a fresh git clone? CB> I've just entered "git pull" and I get the same "Connection CB> reset by peer" error as before. I'm still having this problem CB> -- Colin Baxter m43...@yandex.com CB> - CB> GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 CB> 41C8 CB> - CB> The sole cause of all human misery is the inability of people to CB> sit quietly in their rooms. Blaise Pascal, 1670 -- Samuel W. Flint 4096R/266596F4 (9477 D23E 389E 40C5 2F10 DE19 68E5 318E 2665 96F4) λs.(s s) λs.(s s)
Re: [O] Poll: new keybinding for org-insert-structure-template?
Eric Abrahamsen writes:
> Rasmus writes:
>
>> Eric Abrahamsen writes:
>>
>>> Eric Abrahamsen writes:
>>>
Rasmus writes:
> Kaushal Modi writes:
>
>> On Fri, Dec 15, 2017 at 6:23 AM Rasmus wrote:
>>
>>> The only way it’s "bad" is in the sense it limits the flexibility of
>>> snippets, like ">> block
>>> I can no longer have ">>>
I don't see any way around that. Any system that allows string keys of
arbitrary length is going to run into that problem.
>>>
>>> One possible fix, a bit arbitrary: in the default value, provide
>>> as an artificial "stop key" in the sub-menus. So "s" starts the "source
>>> code" sub-menu, and a after that simply inserts "#+begin_src", and
>>> leaves point after that.
>>
>> Yeah, I tried to suggest that earlier (unless I didn’t say it), but I
>> might not have expressed the idea in an understandable manner :)
>
> Maybe I missed it!
>
>> I think that would be the best approach, but there’s no infrastructure
>> that I know of that does this ATM (but I haven’t had a lot of time lately,
>> so my knowledge on this issue is limited!).
>
> Can't we do this with tempo? It will have to be "handmade", not
> automatic, but:
>
> '(("s" "Source Code")
> ("se" "Elisp" "src elisp")
> ("sp" "Python" "src python")
> ("TAB" "Empty" "src ")
> ...etc
> ("e" "Export Block")
> ("eh" "HTML" "export html")
> ("el" "LaTeX" "export latex")
> ("TAB" "Empty" "export ")
> ...etc
> ("v" "Verbatim" "verbatim")
> ("q" "Quote" "quote")
> ("E" "Example" "example")
> ...etc
> )
Ahem, should have actually tried that first:
(org-mks
'(("s" "Source Code")
("se" "Elisp" "src elisp")
("sp" "Python" "src python")
("s\t" "Empty" "src ")
("e" "Export Block")
("eh" "HTML" "export html")
("el" "LaTeX" "export latex")
("s\t" "Empty" "export ")
("v" "Verbatim" "verbatim")
("q" "Quote" "quote")
("E" "Example" "example"))
"Insert Block" "Block: ")
It's a bit ugly, but it works...
Re: [O] Poll: new keybinding for org-insert-structure-template?
Rasmus writes:
> Eric Abrahamsen writes:
>
>> Eric Abrahamsen writes:
>>
>>> Rasmus writes:
>>>
Kaushal Modi writes:
> On Fri, Dec 15, 2017 at 6:23 AM Rasmus wrote:
>
>> The only way it’s "bad" is in the sense it limits the flexibility of
>> snippets, like "> block
>> I can no longer have ">>
>>> I don't see any way around that. Any system that allows string keys of
>>> arbitrary length is going to run into that problem.
>>
>> One possible fix, a bit arbitrary: in the default value, provide
>> as an artificial "stop key" in the sub-menus. So "s" starts the "source
>> code" sub-menu, and a after that simply inserts "#+begin_src", and
>> leaves point after that.
>
> Yeah, I tried to suggest that earlier (unless I didn’t say it), but I
> might not have expressed the idea in an understandable manner :)
Maybe I missed it!
> I think that would be the best approach, but there’s no infrastructure
> that I know of that does this ATM (but I haven’t had a lot of time lately,
> so my knowledge on this issue is limited!).
Can't we do this with tempo? It will have to be "handmade", not
automatic, but:
'(("s" "Source Code")
("se" "Elisp" "src elisp")
("sp" "Python" "src python")
("TAB" "Empty" "src ")
...etc
("e" "Export Block")
("eh" "HTML" "export html")
("el" "LaTeX" "export latex")
("TAB" "Empty" "export ")
...etc
("v" "Verbatim" "verbatim")
("q" "Quote" "quote")
("E" "Example" "example")
...etc
)
Re: [O] [BUG] Re: header argument :noweb-ref seems can't be resolved
problem solved, Thanks very much. @Nicolas and @Berry. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Wed, Dec 20, 2017 at 8:23 PM, Nicolas Goaziou wrote: > Hello, > > "Berry, Charles" writes: > > > Looks pretty clean. I've not had time to try it out, however. > > Thank you. > > OK. I applied it on master. Since there was some differences with maint, > I didn't backport it there, though. Instead, I bound > `org-babel-current-sourced-block-location' to the current block. > > Hopefully, the problem is now solved. > > Regards, > > -- > Nicolas Goaziou > >
Re: [O] How to include diary anniversary entries into default org-agenda?
Marco Wahl writes: > stardiviner writes: > >> I have an org-mode file: >> >> #+begin_src org >> ,* Anniversary >> >> ,** my first child anniversary >> >> %%(diary-anniversary 10 26 2017) >> >> ,** Funeral Arrangement >> >> ,*** kk >> >> %%(diary-anniversary 12 8 2007) >> #+end_src >> >> How to include and show them in default org-agenda day view by >> configuring org-mode? > > IIUC you can use > > #+begin_src org > ,** my first child anniversary > <%%(org-anniversary 2016 12 20)> > #+end_src > > to get a corresponding entry in the agenda. > > I like keeping anniversaries in bbdb: , | Some Person |mail: some-per...@nowhere.com | anniversary: 1990-01-01 birthday | 2015-01-01 wedding ` and incorporating them into the agenda with , | * Anniversaries | %%(org-bbdb-anniversaries) ` in one of my agenda files. -- Nick
Re: [O] possible to store a link to a specific entry in the *texinfo* file?
Hi yasushi. Thanks for your reply. I am now using org9. Is it possible to specify an exact match? [[info:elisp#define-minor-mode]] gives two potential matches. Found ‘easy-mmode-define-minor-mode’ in Index. (2 total; use ‘,’ for next) Best, On Wed, Dec 20, 2017 at 12:38 PM, Yasushi SHOJI wrote: > Hi, > > I'm sorry that I miss read your question. > > No, org-store-link, or org-info-store-link to be precise, doesn't support > storing the index you just used or you are on. > > I'm not sure how to figure out what a user is trying to store is either > the current node or the index. > > > You can, however, write a link by hand > > [[info:elisp#define-minor-mode]] > > and org is happy to open and jump to the entry > pointed by the index. > > regards, > -- > yashi -- Best, Shiyao
Re: [O] http://orgmode.org/org.html "Short Contents" links seem to be broken
Hi, I can confirm this as an error. The links in the short contents link to anchors starting with "toc_" but these are missing. Maybe they should point to the corresponding parts in the detailed node listing. The links in the pop up toc link directly to the sections in the manual that have anchor names with only the name of the section and theses are working fine. Hope this helps Uwe
Re: [O] [BUG] Re: header argument :noweb-ref seems can't be resolved
Hello, "Berry, Charles" writes: > Looks pretty clean. I've not had time to try it out, however. Thank you. OK. I applied it on master. Since there was some differences with maint, I didn't backport it there, though. Instead, I bound `org-babel-current-sourced-block-location' to the current block. Hopefully, the problem is now solved. Regards, -- Nicolas Goaziou
Re: [O] How to include diary anniversary entries into default org-agenda?
stardiviner writes: > I have an org-mode file: > > #+begin_src org > ,* Anniversary > > ,** my first child anniversary > > %%(diary-anniversary 10 26 2017) > > ,** Funeral Arrangement > > ,*** kk > > %%(diary-anniversary 12 8 2007) > #+end_src > > How to include and show them in default org-agenda day view by > configuring org-mode? IIUC you can use #+begin_src org ,** my first child anniversary <%%(org-anniversary 2016 12 20)> #+end_src to get a corresponding entry in the agenda. HTH Marco
Re: [O] How to include diary anniversary entries into default org-agenda?
I don't know for the agenda, but if you install calfw and calfw-cal, you can see your diary entries in a "more graphical" calendar. On Wed, Dec 20, 2017 at 4:21 AM, stardiviner wrote: > I have an org-mode file: > > #+begin_src org > ,* Anniversary > > ,** my first child anniversary > > %%(diary-anniversary 10 26 2017) > > ,** Funeral Arrangement > > ,*** kk > > %%(diary-anniversary 12 8 2007) > #+end_src > > How to include and show them in default org-agenda day view by configuring > org-mode? > > >
