From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: e-blog.el help please
Date: Fri, 28 Aug 2009 05:33:01 -0700 (PDT) [thread overview]
Message-ID: <a6898b20-d39e-4362-8597-5fc450656b28@a39g2000pre.googlegroups.com> (raw)
In-Reply-To: mailman.5514.1251368830.2239.help-gnu-emacs@gnu.org
On Aug 27, 3:26 am, ken <geb...@mousecar.com> wrote:
> e-blog didn't work for me either. I posted about it months ago, never
> got a reply, so just gave up on it.
>
> --
> War is a failure of the imagination.
> --William Blake
>
> On 08/27/2009 05:58 AM rpd wrote:
>
>
>
> > Hi
> > I want to use e-blog.el to help post to my google blogger blogspot but it
> > doesn't work
> > (curl is installed & works - I am running Vista O/S).
>
> > Here is the error message when I do M-x e-blog-new-post & after I have put
> > in my username & pwd:
>
> > Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> > call-process("curl" nil "*e-blog*" nil "--stderr" "/dev/null" "--header"
> > nil "http://www.blogger.com/feeds/default/blogs")
> > (let (feed) (set-buffer e-blog-buffer) (erase-buffer) (message "Requesting
> > list of blogs...") (call-process "curl" nil e-blog-buffer nil "--stderr"
> > "/dev/null" "--header" e-blog-auth e-blog-fetch-bloglist-url) (setq feed
> > (buffer-substring ... ...)) (message "Requesting list of blogs... Done.")
> > feed)
> > e-blog-fetch-bloglist()
> > (e-blog-parse-xml (e-blog-fetch-bloglist))
> > (e-blog-setup-choose-buffer (e-blog-parse-xml (e-blog-fetch-bloglist)))
> > e-blog-choose()
> > (if (e-blog-check-authinfo) (e-blog-choose))
> > e-blog-do-auth()
> > (progn (e-blog-do-auth) (e-blog-choose))
> > (if e-blog-auth (e-blog-choose) (progn (e-blog-do-auth) (e-blog-choose)))
> > e-blog-new-post()
> > call-interactively(e-blog-new-post)
> > execute-extended-command(nil)
> > call-interactively(execute-extended-command)
>
> > Can anyone help me fix this please?
>
> > (I saw this on internet search & tried it but it didn't work:
> > ;;e-blog.el Blogger with Emacs in Windows
> > ;;http://deepakramani.home.comcast.net/~deepakramani/Blog/2009/07/blogg...
> > ;;1.Comment lines that read: "--stderr" "/dev/null"
> > ;;2.Beneath the commented lines add the line "--insecure"
> > ;;This isn't ideal, since the communication is not secure, but it works fine
> > for me.
>
> > ;;-Well no-it didn't work for me!so I have switched back! )
>
> > Many thanks
guys, please post a issue at e-blog home page here:
http://code.google.com/p/e-blog/issues/list
that way the author is at least aware that there are many requests.
Whether he's gonna find time to fix is another issue.
i was enthusiatic about e-blog a year ago. It worked for plain text
blog, but doesn't work if your blog is slightly complicated html.
Since i need to use full html, so i stopped using e-blog. I simply use
the dedicated browser these days.
Xah
∑ http://xahlee.org/
☄
next prev parent reply other threads:[~2009-08-28 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 9:58 e-blog.el help please rpd
2009-08-27 10:26 ` ken
[not found] ` <mailman.5514.1251368830.2239.help-gnu-emacs@gnu.org>
2009-08-28 12:33 ` Xah Lee [this message]
[not found] <mailman.5509.1251367107.2239.help-gnu-emacs@gnu.org>
2009-08-27 11:24 ` Anselm Helbig
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6898b20-d39e-4362-8597-5fc450656b28@a39g2000pre.googlegroups.com \
--to=xahlee@gmail.com \
--cc=help-gnu-emacs@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.
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).