On 01/08/2011 09:21 AM, Dave Taht wrote:
> On 01/06/2011 09:06 AM, Allen S. Rout wrote:
> 3) Going from the Emacs org (or markdown) UI to "webspace" is really
> disconcerting for me. My fingers do emacs, my eyeballs like green on
> white,
Correction:
green on *black*... the white of most web pag
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
On 01/06/2011 09:06 AM, Allen S. Rout wrote:
> Dave Taht writes:
>
>> So over the holiday I wrote a command line web search client with an
>> emacs interface and called it "gnugol". It uses the google json and bing
>> json APIs to search the web, and outputs the results in plain text, in
>> whate
I know--the "*eshell*" is not necessary too--its illustrative--its just an
example--showing that you could (using your new module) create
multiple asynchronous/coprocesses (in their own dedicated buffers) uniquely
named shells and maybe make calls out to goosh and use surfraw and/or gnugol
somehow.
On 6 Jan 2011, at 19:19, brian powell wrote:
** Example/possibilities:
apt-get install surfraw
...
[[eshell:*eshell*:(rename-buffer "vvv")]]
[[eshell:*eshell*:(rename-buffer "ttt")]]
There's no need for those two lines, because...
[[eshell:vvv:date]]
... this one will create the eshell buf
I'll see you're surfraw; and, I'll raise you a goosh:
http://goosh.org
---maybe gnugol could work with goosh somehow?
---works from an Emacs Shell/eshell too:
** Example/possibilities:
apt-get install surfraw
...
[[eshell:*eshell*:(rename-buffer "vvv")]]
[[eshell:*eshell*:(rename-buffer "ttt")]]
Dave Taht writes:
> So over the holiday I wrote a command line web search client with an
> emacs interface and called it "gnugol". It uses the google json and bing
> json APIs to search the web, and outputs the results in plain text, in
> whatever format you're working in, notably, org, so you ca
Dave Taht writes:
> A fix for one of the problems reported on this list (by bart, thx!) was
> to make sure that the path
>
> /usr/local/lib
>
> was in /etc/ld.so.conf or in /etc/ld.so.conf.d and to run
>
> sudo ldconfig
>
> after installing libjannson.
>
> I've updated the documentation to reflect
Hi Dave,
Dave Taht writes:
> On 01/04/2011 01:17 AM, Bastien wrote:
>> Looks interesting!
>
> It's so awesome to have people trying this - my last project had 2 users
> total
I agree that this looks very interesting. Thanks!
>> I'm using ArchLinux. I installed jansson from `yaourt -S jan
Hi Achim,
I had made the silly mistake of not remembering to run ldconfig. Once
this was done the janson libraries were found and gnugol started working
for me.
Apollogies I didn't get around to posting the fix/thing to remember
earlier.
Thank you very much though for the information, it has ta
Bart Bunting writes:
> Running into a few issues at the moment: I did download and build the
> jansson library which is installed in /usr/local
>
> However when I run gnugol I'm seeing the following error:
>
> Errors: google(1): ../engines/google.so: cannot open shared object file: No
> such fi
11 matches
Mail list logo
