From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: send agenda-weekly-view via email html formated
Date: Sun, 31 Oct 2021 10:37:56 +0100 [thread overview]
Message-ID: <87tugxttzf.fsf@mat.ucm.es> (raw)
In-Reply-To: 87zgqptu5c.fsf@mat.ucm.es
[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]
>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:
>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:
>> Ihor Radchenko <yantar92@gmail.com> writes:
>>> Uwe Brauer <oub@mat.ucm.es> writes:
>>>
>>> I know I can save my weekly agenda view as a HTML file and then send it as as attachment.
>> Sorry, I misread your first message. Attaching and sending is easy:
>> (defun org-agenda-email ()
>> "Email agenda in current buffer as attachment."
>> (interactive)
>> (let ((to (read-string "Send to: "))
>> (subject (read-string "Subject: ")))
>> (unless (derived-mode-p 'org-agenda-mode) (user-error "Should start from agenda view."))
>> (org-agenda-write (file-name-concat (temporary-file-directory) "agenda.html") nil nil (current-buffer))
>> (compose-mail to subject)
>> (save-excursion
>> (goto-char (point-max))
>> (mml-attach-file (file-name-concat (temporary-file-directory) "agenda.html")))))
> Thanks I run a test in an org-agenda and obtained
> ,----
> |
> | Debugger entered--Lisp error: (void-function file-name-concat)
> | (file-name-concat (temporary-file-directory) "agenda.html")
> | (org-agenda-write (file-name-concat (temporary-file-directory) "agenda.html") nil nil (current-buffer))
> | (let ((to (read-string "Send to: ")) (subject (read-string
> | "Subject: "))) (if (derived-mode-p 'org-agenda-mode) nil (user-error
> | "Should start from agenda view.")) (org-agenda-write
> | (file-name-concat (temporary-file-directory) "agenda.html") nil nil
> | (current-buffer)) (compose-mail to subject) (save-excursion
> | (goto-char (point-max)) (mml-attach-file (file-name-concat
> | (temporary-file-directory) "agenda.html"))))
> | org-agenda-email()
> | funcall-interactively(org-agenda-email)
> | apply(funcall-interactively org-agenda-email nil)
> | repeat-complex-command(1)
> | funcall-interactively(repeat-complex-command 1)
> | call-interactively(repeat-complex-command nil nil)
> | command-execute(repeat-complex-command)
> `----
I debugged it the problem is file-name-concat.
I am running Emacs master 83a915d3dfafd5f3d737afe
not too old, I'd say
But that function is not defined.
😇
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-10-31 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 8:09 send agenda-weekly-view via email html formated Uwe Brauer
2021-10-31 8:33 ` Ihor Radchenko
2021-10-31 8:47 ` Ihor Radchenko
2021-10-31 9:34 ` Uwe Brauer
2021-10-31 9:37 ` Uwe Brauer [this message]
2021-10-31 9:58 ` Ihor Radchenko
2021-10-31 9:42 ` Ihor Radchenko
2021-10-31 9:58 ` Uwe Brauer
2021-10-31 10:07 ` Ihor Radchenko
2021-11-01 9:26 ` Uwe Brauer
2021-11-01 12:58 ` Ihor Radchenko
2021-11-01 14:03 ` Uwe Brauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tugxttzf.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).