From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim X Newsgroups: gmane.emacs.help Subject: Re: Emacs accessing a mediawiki through an "automatice proxy configuration url"? Date: Fri, 27 Apr 2007 17:15:18 +1000 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <87r6q6thix.fsf@lion.rapttech.com.au> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1177659269 29819 80.91.229.12 (27 Apr 2007 07:34:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 27 Apr 2007 07:34:29 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Apr 27 09:34:26 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HhKyI-0000gs-D8 for geh-help-gnu-emacs@m.gmane.org; Fri, 27 Apr 2007 09:34:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HhL47-0003M0-1Y for geh-help-gnu-emacs@m.gmane.org; Fri, 27 Apr 2007 03:40:27 -0400 Original-Path: shelby.stanford.edu!newshub.stanford.edu!postnews.google.com!news4.google.com!sn-xt-sjc-04!sn-xt-sjc-07!sn-post-sjc-01!supernews.com!corp.supernews.com!not-for-mail Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (gnu/linux) Cancel-Lock: sha1:/rVUf8Tiq/ll9kp2PnVuUfC6u1c= Original-X-Complaints-To: abuse@supernews.com Original-Lines: 46 Original-Xref: shelby.stanford.edu gnu.emacs.help:147657 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:43261 Archived-At: Galen Boyer 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 - 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. Tim -- tcross (at) rapttech dot com dot au