Thorsten Jolitz <tjol...@gmail.com> writes: > Eric Abrahamsen <e...@ericabrahamsen.net> writes: > >> Thorsten Jolitz <tjol...@gmail.com> writes: >> >>> Eric Abrahamsen <e...@ericabrahamsen.net> writes: >>> >>>> I'm trying to write a small function that programmatically follows a >>>> link to a gnus message, then calls >>>> `gnus-summary-wide-reply-with-original' to start a reply to that >>>> message. It seemed like `org-open-link-from-string' (after extracting >>>> the address part from the link) would be the right choice, but I'm >>>> seeing odd behavior. > > [...] > >>> #+begin_src emacs-lisp >>> (defun org-open-link-from-string (s &optional arg reference-buffer) >>> "Open a link in the string S, as if it was in Org-mode." >>> [...snip...] >>> (org-open-at-point arg reference-buffer))))) >>> #+end_src >>> >>> ,---------------------------------------------------------------------- >>> | org-open-at-point is an interactive Lisp function in `org.el'. >>> | >>> | (org-open-at-point &optional ARG REFERENCE-BUFFER) >>> | >>> | Open link at or after point. >>> | If there is no link at point, this function will search forward up to >>> | the end of the current line. >>> | Normally, files will be opened by an appropriate application. If the >>> | optional prefix argument ARG is non-nil, Emacs will visit the file. >>> | With a double prefix argument, try to open outside of Emacs, in the >>> | application the system uses for this file type. >>> `---------------------------------------------------------------------- >>> >>> Maybe because you call >>> >>> ,--------------------------------- >>> | (org-open-link-from-string addr) >>> `--------------------------------- >>> >>> without ARG, Emacs is not visiting the file and thus its buffer does not >>> become current? >> >> Huh, interesting -- I had looked at that function, and assumed that the >> what the arg did was to force a file that might otherwise be opened by >> an external process to be opened in emacs. I still think that's what it >> means (and adding a '(4) doesn't solve the problem), but there's other >> stuff in there that might lead to a solution. > > Yes, you are right about the meaning of ARG, I should have looked twice. > >>> Anyway, when you're done - please share, this is quite interesting. >> >> I will! It's pretty much done, except for this one little bug. > > I can imagine that this is very useful for managing phonecalls to be > made in the future...
Well this will only cover composing and replying to emails, but if you have a function that automatically makes a phone call, I suppose it would serve as a template... Mostly I'm doing it because a full half of my work seems to be replying to interminable emails, and I wanted something that would keep me in the agenda as much as possible: hit a key on a TODO, type the email, send it, and there you are back in the agenda again. It's turning out to be a little more complicated than I thought!