emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dave Taht <d@teklibre.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Introducing gnugol - an org-mode-output web search client
Date: Sat, 08 Jan 2011 09:42:49 -0800	[thread overview]
Message-ID: <4D28A219.5000603@teklibre.org> (raw)
In-Reply-To: <AANLkTinWkv+6NG0hUfFCadDuKSEXjqkZ924t-05u1UoA@mail.gmail.com>

On 01/06/2011 10:19 AM, brian powell wrote:
> I'll see you're surfraw; and, I'll raise you a goosh:
> 
> http://goosh.org

Cute!

> ---maybe gnugol could work with goosh somehow?

Not unless it went green on white!

> ---works from an Emacs Shell/eshell too:
> 
> ** Example/possibilities:
> apt-get install surfraw
> ...
> [[eshell:*eshell*:(rename-buffer "vvv")]]
> [[eshell:*eshell*:(rename-buffer "ttt")]]
> [[eshell:vvv:date]]
> [[eshell:ttt:sr wikipedia goosh]]

I see where you are going with this and I like it. One conceptual
problem here is the meta-data format. Shell commmand line has the idea
of argument separators as spaces and strings. Although utf-8 almost
works well at the command line, I would have liked it if unicode had
given programmers their own glyph and character set to work in, so we
wouldn't have to go so crazy escaping the concepts that we'd wedged into
ASCII in the 80s.

BUT html/xml have a totally different concept of metadata than that, as
does org-mode...

json comes close to being a command line format that could be parsed
using conventional piping/filters.

In the beginning I thought I'd have gnugol output Lisp forms and the
interface be more like bbdb.  There is a pretty clean json parser for
emacs however, and I've been thinking of using that.

> ---provided you have the new org-eshell.el

I didn't know this existed, cool, I'll fiddle.

  parent reply	other threads:[~2011-01-08 17:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-02 23:28 Introducing gnugol - an org-mode-output web search client Dave Taht
2011-01-03  5:00 ` Bart Bunting
2011-01-04 10:06   ` Achim Gratz
2011-01-04 10:21     ` Bart Bunting
2011-01-04  9:17 ` Bastien
2011-01-04  9:57   ` Manuel Hermenegildo
2011-01-04 19:11   ` Dave Taht
2011-01-05  2:05     ` Matt Lundin
2011-01-05  8:40     ` Achim Gratz
2011-01-06 17:06 ` Allen S. Rout
2011-01-06 18:19   ` brian powell
2011-01-06 20:11     ` Konrad Hinsen
2011-01-07 11:35       ` brian powell
2011-01-08 17:42     ` Dave Taht [this message]
2011-01-08 17:21   ` Dave Taht
2011-01-08 18:12     ` Dave Taht

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=4D28A219.5000603@teklibre.org \
    --to=d@teklibre.org \
    --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).