From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: intranet blogging from emacs
Date: Sat, 21 Mar 2009 17:26:02 -0700 (PDT) [thread overview]
Message-ID: <14a8e44e-5a73-415a-90d6-6ebd4a878f30@y33g2000prg.googlegroups.com> (raw)
In-Reply-To: mailman.3713.1237637138.31690.help-gnu-emacs@gnu.org
On Mar 21, 5:05 am, Rustom Mody <rustompm...@gmail.com> wrote:
> I am exploring lightweight options for creating an (intranet) blog of my
> team members.
> What are the options for pushing out from emacs to a blog-publish share
> location?
here's some info might be useful to you:
• e-blog by Mikey Coulson works great with google blog (blogger).
• LjUpdate package by Edward O'Connor works fantastic for livejournal.
Others i've tried: blogger.el and WebloggerMode, does not work for me.
Also, emacspeak supposed to work with blogger too, but i've read from
blogs recently that it's also problematic.
For some detail about these:
• A Emacs Frustration (blogger package)
http://xahlee.org/UnixResource_dir/writ/emacs_blogger_package_pain.html
----------
depending on what your intranet blog is...
w3m is primarily a text-based browser like lynx, launched from command
line.
http://en.wikipedia.org/wiki/W3m
Emacs has a interface to it, called w3m, so that you can browse web in
emacs.
from my experience, this combination is actually some 5 times slower
than full featured web browsers. (my w3m has image loading turned
off, while my web browser has images on, and js and css on.)
today, js is almost a requirement for most major sites. Without js
support, w3 can't use many sites.
personally i use w3m occasionally for my work involving dictionary
lookup. Overall, i don't recommend it, because you have spend hours or
days to install, learn to use it, and on the whole the benefit isn't
great. (e.g. compared to a browser, some 5 times slower, no js, ugly
display, and often badly formed, and so on)
as other suggested, you could just use w3m to update your blogs thru
the standard web interface. However, i've not tried this.
In fact, these days i simply use full featured browser to update my
blogger blogs. I find it faster, more convenient, in general, then
trying to do it within emacs. Typically, one button press switch me to
browser, few clicks with the interface gets me to the blog update
page, one button switch me to emacs, write, switch, paste, click to
update. Repeat if necessary, or use any of the editing or admin
features in the blog interface, which usually won't be there in any
integrated emacs blog uploading modes.
part of the reason that web interface works better in general for me,
besides above reasons, is that usually my blog writing involves
complicated html (such as css marked syntax coloring of code
snippets), and sometimes plain text mixed with the particular mark-
down and html (such as links). The simplified mark-up lang used for
each blog site are different (and there's no one standard or
predominant one). The emacs blog modes typically support plain text
only. Any extra features available on the blog, such as the extensive
admin and blog archive editing or comment management etc provided by
google's blogger, is not there.
Xah
∑ http://xahlee.org/
☄
next prev parent reply other threads:[~2009-03-22 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3713.1237637138.31690.help-gnu-emacs@gnu.org>
2009-03-21 14:14 ` intranet blogging from emacs Jim Burton
2009-03-21 16:10 ` rustom
2009-03-21 17:28 ` Pascal J. Bourguignon
2009-03-22 0:26 ` Xah Lee [this message]
2009-03-22 2:49 ` Jason Rumney
2009-03-25 8:45 ` Torsten Senf
2009-03-21 12:05 Rustom Mody
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=14a8e44e-5a73-415a-90d6-6ebd4a878f30@y33g2000prg.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).