From: Galen Boyer <galen_boyer@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs accessing a mediawiki through an "automatice proxy configuration url"?
Date: 12 May 2007 21:19:03 -0500 [thread overview]
Message-ID: <u4pmh5lsu.fsf@rcn.com> (raw)
In-Reply-To: 87r6q6thix.fsf@lion.rapttech.com.au
On Fri, 27 Apr 2007, timx@nospam.dev.null wrote:
> Galen Boyer <galen_boyer@yahoo.com> writes:
>
>> I can browse our internal company wiki with w3m but when I hit enter
>> for editing, emacs does not recognize the editing section of the
>> buffer as editable. Any places I can look for customization hints?
>> Any different paths I should take? ...
>>
>
> What you describe sounds like your company's wiki must be using a
> javascript based wiki
Hm... Okay. I'll have to research a bit to see if this is the case.
> - thats the only reason I can think of that w3m can't be used to
> update it.
>
> I've been thinking about a similar problem lately. I would like to be
> able to update our company wiki from within emacs rather than from
> within another browser and I'd like a nicer environment than you would
> get just inside a w3m form text area.
>
> A couple of things have come to mind. There is a wiki (PMWiki) which
> has an emacs mode you can use to update the wiki. I've not tried it,
> but I suspect it might be a good source of ideas for writing some mode
> that would work with our company's wiki.
>
> One of the problems with wikis is that many have now incorporated
> extensions beyond the basic/initial wiki markup. This makes a generic
> wiki mode unlikely. However, there is also a lot of commonality which
> we should be able to exploit.
>
> One idea I've been thinking about is to identify the specific wiki
> "rules" of our company wiki and possibly defining a compatible
> 'publish' mode for emacs muse-mode. I don't think this would be
> particularly hard and would provide a nice environment for creating
> new pages for the wiki. However, there is also the requirement of
> being able to retrieve existing pages and update them. This would need
> some sort of reverse translation from the wiki language being used
> into muse-mode markup, which you could then edit and re-publish in the
> markup the wiki understood.
>
> emacs 22 has the url package that use to be part of w3 and there are
> interfaces to wget and curl, so it shouldn't be too hard to find a way
> of moving pages in/out (there is also emacs webdav interface).
>
> I expect it wouldn't be to hard to achieve a nice emacs based mode for
> editing a wiki as long as that wiki isn't too feature rich.
You've thought alot deeper about this than I. I'd just like to be able
to use Emacs as my only interface to our wiki, even if I just have a
text box.
I did download the Mozilla extension, 'It's all text". A different
thread recommended it. It allowed me to edit the wiki with Emacs but
browse with Mozilla. Certainly better than no Emacs at all.
--
Galen Boyer
next prev parent reply other threads:[~2007-05-13 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 3:25 Emacs accessing a mediawiki through an "automatice proxy configuration url"? Galen Boyer
2007-04-27 7:15 ` Tim X
2007-05-13 2:19 ` Galen Boyer [this message]
2007-05-19 19:13 ` Lukasz Stafiniak
2007-05-19 19:32 ` Lukasz Stafiniak
2007-05-22 21:45 ` Xavier Maillard
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=u4pmh5lsu.fsf@rcn.com \
--to=galen_boyer@yahoo.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).