Re: [O] Solar orbit statistics and your agenda

2018-11-20 Thread Eric S Fraga
On Tuesday, 20 Nov 2018 at 11:12, Alan E. Davis wrote:
> Eric:
>
> This is extremely useful.   

Glad you liked it.  Strangely enough, they seem to have changed the
format of output (now sending json) so the script no longer works.

> I found some documentation on the site, re the API.

What is the link for the API information?  With that, I may be able to
help answer your question about getting lunar declination data off the
server.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442



Re: [O] [RFC] Org Num library

2018-11-20 Thread Eric S Fraga
On Tuesday, 20 Nov 2018 at 19:22, Nicolas Goaziou wrote:
> Since it is very much Org-specific, and a basic feature you could expect
> from Org, I'd like to add it in core. So, if there is no strong
> objection to it, it can go in Org 9.3.

No objection from me at all.  I may or may not use this very often but see no 
reason it cannot be there for others to use.

It does seem to work very well, by the way.

thanks,
eric
-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442



Re: [O] [RFC] Org Num library

2018-11-20 Thread Neil Jerram
Nicolas Goaziou  writes:

> Since it is very much Org-specific, and a basic feature you could expect
> from Org, I'd like to add it in core. So, if there is no strong
> objection to it, it can go in Org 9.3.
>
> I attach the library for further testing, suggestions, remarks… Let me
> know what you think.

Well, with my Org 9.1.14, I can report that the code evaluates cleanly
and the feature works.  I can't see any objection to adding it into
core.

(I'd add that I'm not yet seeing a clear use case for it; but perhaps
that will change in future.)

 Neil



Re: [O] suppress ++ markup in orgmode?

2018-11-20 Thread John Kitchin
That doesn't seem right to me. It seems like a bug that it is rendered as
strikethrough to me, like the regexp that is generated is too greedy. That
was a good hint though.

I was able to add + to the border component of the regexp components which
seems to have fixed the problem for me for now.

(setq org-emphasis-regexp-components '("- ('\"{"   ;pre
   "- .,:!?;'\")}\\["  ;post
   "\\+
" ;border
   "."
   1))

John

---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



On Tue, Nov 20, 2018 at 12:54 PM Berry, Charles  wrote:

>
>
> > On Nov 19, 2018, at 6:08 PM, John Kitchin 
> wrote:
> >
> > I was looking at https://github.com/joostkremers/criticmarkup-emacs
> again recently and ran into something I don't recall happening before.
> >
> > There is a markup for inserting text thatlooks like {++Insert this
> text++}. However, in org-mode this is marked up as strikethrough. Is there
> a way to make that not happen?
> >
>
>
>
> customize org-emphasis-alist I would think
>
> HTH,
>
> Chuck
>


Re: [O] Solar orbit statistics and your agenda

2018-11-20 Thread Alan E. Davis
Eric:

This is extremely useful.   I found some documentation on the site, re the
API.  I am way over my head here, but I need (for one) data on Lunar
Declination over, say, a year, but really month-by-month.  Is there a "for
Dummies" to get this data off of this server?  A cookbook?  Can I do
something like this?

grep -E 'oon&' >${tmpfile}

?

Thank you again.





On Wed, Nov 7, 2018 at 5:59 AM Eric S Fraga  wrote:

> Time for a very geeky post...
>
> Recently, on the remind (diary tool I used to use) mailing list,
> somebody posted a script for converting solar data (perihelion, equinox,
> ...) to remind input.  I've done the same for org so if you're
> interested in that kind of information and want your agenda to show
> this, here is the script:
>
> #+begin_src shell :results output raw
>   tmpfile=$(mktemp /tmp/date.XX)
>   for year in $(seq 2018 2068)
>   do
>   links http://aa.usno.navy.mil/seasons?year=${year} -dump | \
>   grep -E 'helion|quinox|olstice' > ${tmpfile}
>   while read -r line
>   do
>   item=$(echo $line | awk '{print $1}')
>   date="$(echo $line | awk '{print $5 " " $4 " " $3}') ${year}"
>   isodate=$(date --date="${date}" +"%Y-%m-%d %H:%M")
>   echo "** <${isodate}> $item"
>   done < ${tmpfile}
>   done
>   rm ${tmpfile}
> #+end_src
>
> Notes:
>
> 1. this is for Linux and assumes bash as the shell.
> 2. the default is UTC (and this is where I wish org supported time
>zones...).
> 3. I believe the URL for the US Naval Observatory in the code above
>accepts "?tz=N?dst=M" for different time zones (some index N) and
>daylight savings options (M set to 0 or 1 maybe?) but I haven't
>played with these options.
> 4. you will need to install "links".
>
> Enjoy but use at own risk etc. ;-)
>
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.1.11-620-ga548e4
>
>

-- 
[Fill in the blanks]

The use of corrupt manipulations and blatant rhetorical ploys ...---
outright lying, flagwaving, personal attacks, setting up phony
alternatives, misdirection, jargon-mongering, evading key issues, feigning
disinterested objectivity, willful misunderstanding of other points of
view---suggests that ... lacks both credibility and evidence.

  Edward Tufte (in context of making presentations)


[O] [RFC] Org Num library

2018-11-20 Thread Nicolas Goaziou
Hello,

A few weeks ago, I posted on this ML a proof of concept about dynamic
numbering of headlines in an Org buffer. Since then, I worked on it more
seriously, improved it, and threw in some features. Here is an excerpt
of its commentary section:

This library provides dynamic numbering for Org headlines.  Use
   

   
to toggle it.
   
You can select what is numbered according to level, tags, COMMENT
keyword, or UNNUMBERED property.  You can also skip footnotes
sections.  See `org-num-max-level', `org-num-skip-tags',
`org-num-skip-commented', `org-num-skip-unnumbered', and
`org-skip-footnotes' for details.
   
You can also control how the numbering is displayed by setting
   `org-num-face' and `org-num-format-function'.

I tested it a bit, even in relatively large documents like the Org
manual, without problem. I also wrote a test suite for that library.

Since it is very much Org-specific, and a basic feature you could expect
from Org, I'd like to add it in core. So, if there is no strong
objection to it, it can go in Org 9.3.

I attach the library for further testing, suggestions, remarks… Let me
know what you think.

Regards,

-- 
Nicolas Goaziou


org-num.el
Description: Org Num library


Re: [O] suppress ++ markup in orgmode?

2018-11-20 Thread Berry, Charles



> On Nov 19, 2018, at 6:08 PM, John Kitchin  wrote:
> 
> I was looking at https://github.com/joostkremers/criticmarkup-emacs again 
> recently and ran into something I don't recall happening before.
> 
> There is a markup for inserting text thatlooks like {++Insert this text++}. 
> However, in org-mode this is marked up as strikethrough. Is there a way to 
> make that not happen? 
> 



customize org-emphasis-alist I would think

HTH,

Chuck



Re: [O] FW: [RFC] Link-type for attachments, more attach options

2018-11-20 Thread Ihor Radchenko
Hi,

>Generalize org-agenda by allowing us to have multiple ones, and make them 
> more general by thinking of them as a set of views that works on sets of 
> files. Maybe this is not for all, but I would appreciate to create multiple 
> "agendas" (even though I'd call them "libraries" in instead), and possibly 
> also an aggregate agenda consisting of other agendas.

Isn't this already in org? You can use custom agendas with multiple
"agendas" (custom commands) and set the files they operate on with
org-agenda-files within custom commands.

>If two org-mode files exist in the same folder with different names, it 
> would be awesome to think of (and work with) them as two top-level headings 
> inside one org-mode buffer. Similar to two level-1 headings inside an 
> org-mode file. For this to work all properties we can define for regular 
> headings should be possible to define for these "level-0 headings". For 
> example an attachment-folder or ID, a deadline, scheduled date, or 
> TODO-keyword should in that case be configurable on the whole file. I guess 
> some new conventions regarding syntax and existing properties would have to 
> be created as well.

You can do something like below. It is pretty much what you want, except
I am not sure how to update the headings from local org files. Current
org version does not allow `:results replace` on raw org output.

* Main heading

#+name: org-files-here
#+begin_src bash
ls *.org
#+end_src

#+begin_src emacs-lisp :var files=org-files-here()  :var stars=(make-string 
(car (org-heading-components)) ?*)  :results raw replace drawer
(let ((files (mapcar #'car files)))
  (cl-loop for file in files
   concat (with-current-buffer (find-file-noselect file)
(concat (format "* %s\n" (buffer-file-name))
(replace-regexp-in-string "^\\*" (concat "*" stars) 
(buffer-string))
#+end_src

Best,
Ihor

Gustav Wikström  writes:

> Hi,
>
>> -Original Message-
>> From: Ihor Radchenko 
>> Sent: den 18 november 2018 01:42
>> To: Gustav Wikström ; Marco Wahl
>> 
>> Cc: emacs-orgmode 
>> Subject: RE: [O] FW: [RFC] Link-type for attachments, more attach options
>> 
>> Hi Gustav,
>> 
>> > I like the idea of a function that would symbolically links folders
>> > from "ID"-folder structure to a hierarchy-folder structure, based on
>> > the name and path of the org-file  and its headings containing the
>> > links. I probably wouldn't use it much myself though. Not until
>> > org-mode starts working better with multiple files, allowing us to
>> > more easily define "org-mode libraries".
>> 
>> I am wondering what you mean by "org-mode libraries". Can you explain
>> further?
>
> This goes a bit off topic; But what I mean is mainly two things: 
> 1) Generalize the org-agenda so that we can have multiple ones
>
>Generalize org-agenda by allowing us to have multiple ones, and make them 
> more general by thinking of them as a set of views that works on sets of 
> files. Maybe this is not for all, but I would appreciate to create multiple 
> "agendas" (even though I'd call them "libraries" in instead), and possibly 
> also an aggregate agenda consisting of other agendas.
>
> 2) Make files function as virtual "level-0 headings"
>
>If two org-mode files exist in the same folder with different names, it 
> would be awesome to think of (and work with) them as two top-level headings 
> inside one org-mode buffer. Similar to two level-1 headings inside an 
> org-mode file. For this to work all properties we can define for regular 
> headings should be possible to define for these "level-0 headings". For 
> example an attachment-folder or ID, a deadline, scheduled date, or 
> TODO-keyword should in that case be configurable on the whole file. I guess 
> some new conventions regarding syntax and existing properties would have to 
> be created as well.
>
>> 
>> Also, another thought about the attachment: links.
>> It would be useful to implement links to attachments, which are not in the
>> current org entry.
>> For example, something like "attachment:ORG-ID:file-name", where ORG-ID
>> refers to ID of an arbitrary org entry.
>
> I wouldn't call that attachment-links, but rather ID-based links (since 
> attachments are local based on either headline ID or attach-dir of the 
> current headline). ID links exist already but link to headlines. 
>
> If you rather see ID-based attachments as some kind of global attachments for 
> all your org-mode files, I'd think the link-type should reflect that and be 
> called something like "ID-attachment:file-name", "ID-@:file-name", 
> "@ID:file-name" and be a separate link-type.
>
>> 
>> Best,
>> Ihor
>> 
>> 
>
> Kind regards
> Gustav



signature.asc
Description: PGP signature