Re: ioccur incremental occur

Ted Zlatanov <tzz <at> lifelogs.com> writes:

> On Tue, 09 Mar 2010 08:05:01 +0100 Thierry Volpiatto <thierry.volpiatto <at> gmail.com> wrote: 
>
> TV> find here ioccur, a clone of occur but incremental.
>
> TV> It have his own history, empty when you will start of course.
>
> You may want to enable next-error functions in the ioccur mode.  See
> the occur, grep, or compile modes in Emacs for examples.  Basically this
> is so users can bind keys to next-error and previous-error and then move
> between ocurrences in various modes in a consistent way.

Thanks to point me on that, however ioccur is different of occur:

It can destroy the ioccur-buffer after a search.

When keeping buffer, the ioccur-buffer are named, so you can have more
than one ioccur-buffer, each ioccur-buffer dedicated to a particular
buffer.

If i bind the next-error system in ioccur, i imagine it will recall
only the search made in the last ioccur-buffer recorded, so i wonder if
it is really useful?
But maybe i am wrong, anyway i will think at it.

BTW version 1.3 is available, no more features, only bugfix, find it
attached here for commodity, and also here as usual:

hg clone http://mercurial.intuxication.org/hg/ioccur

Re: [emacs] emacs text translator

>>>>> On Mon, 8 Mar 2010 05:27:56 -0800 (PST), Andreo <andreytorba <at> gmail.com> wrote:

   > Hi all,
   > There is an emacs module for text translation using google api:

   > http://github.com/andreo/google-translator
do you know about babel.el. Does the same thing.

Uwe Brauer 

Re: [emacs] emacs text translator

Google translator is Software as a Service -- see
http://www.gnu.org/philosophy/who-does-that-server-really-serve.html.

Re: ga.el 0.4 Release

Andreas <xxtjaxx <at> googlemail.com> writes:

   > Ga is a generic apt(as used in Debian GNU/Linux) alike interface over
   > various package management tools.

   Does that mean one could hook that up to a service and download and
   install EMACS extension packages this way? Like an apt that runs for
   emacs extensions?

I don't know if i understand you correctly.  Ga is basically a wrapper
of command line tools, such as apt-get, yum, pkgsrc, etc.  If you write
an apt-emacs command, of course we can hook it to Ga.  

--

-- 
William

http://xwl.appspot.com

checkdoc-batch.el v.3

This spot of code runs M-x checkdoc in "batch" style, giving a report of
problems instead of going through interactively fixing them.

The implementation is diabolical, but it's very handy for checking a big
set of lisp files in one go.

A happy side effect is that it avoids the way for interactive
M-x checkdoc an "n" means "next docstring" not "no I don't want to fix
this thing".  Answering "n" can make you miss subsequent problems if you
don't want to fix the first.

#!/bin/sh

# emacs-checkdoc-batch -- run checkdoc-batch.el on lisp files
#
# Copyright 2010 Kevin Ryde
#
# emacs-checkdoc-batch is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License as published
# by the Free Software Foundation; either version 3, or (at your option)
# any later version.
#
# emacs-checkdoc-batch is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General
# Public License for more details.
#

BBDB or BADB (born again database)

I thought I can post this here.

Is this BBDB or BADB (the born-again database)? I don't know!

BBDB had been dormant for quite some time. Actually, I never used it.
When I looked at it, the code appeared rather rusted to me,
a software package that had grown organically over many years
(many years ago), making it difficult to make new changes to it. Yet at
some point I thought I needed something of that kind to keep track of
names, phone numbers, email and snail mail addresses and what else.

When I tried to get BBDB working for me, I ended up doing much more
changes than I had ever expected. 

- I didn't try to keep any backward compatibility (beyond the latest
  GNU Emacs released a few days ago), nor did I try to keep the code
  compatible with Xemacs (which I don't know / don't use). (Yet I
  could even imagine that it is not so difficult to port the new code.)

- I gave up to write a ChangeLog, changes were too numerous.

- I tried to give variables and functions more consistent names. If
  you have any old customizations of BBDB, most likely they will not
  work with the code below! (Yet maybe you want to agree with me
  that it might have become easier to add new ones.)

- Also, I tried to give functions and commands more consistent
  calling sequences.

- Many changes of variable and function names were done on all files

Re: ioccur incremental occur

Hi all,
as always, version 1.4 of ioccur is available at

hg clone http://mercurial.intuxication.org/hg/ioccur

Find it attached it here also.

No more features but it is much more fast now.

--

-- 
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/

_______________________________________________
gnu-emacs-sources mailing list
gnu-emacs-sources <at> gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources

Re: BBDB or BADB (born again database)

"Roland Winkler" <Roland.Winkler <at> physik.uni-erlangen.de> writes:

>
> PS: How to use these files? Compile them with make, and put them
> into your emacs loadpath. Then the command bbdb is kind of a generic
> starting point. The menus show you many commands that you can use.
>

Here's what I get:

DBoyd <at> FLM000025LVE9F ~/.emacs.d/bbdb-3.0
$ make
Wrote /cygdrive/c/cygwin/home/DBoyd/.emacs.d/bbdb-3.0/bbdb.elc
Cannot open load file: .././loadpath.el
make: *** [bbdb-com.elc] Error 255

Where did you put _your_ files to compile them?

Dave

Re: BBDB or BADB (born again database)

I suggest to continue these discussions on the list
bbdb-info <at> lists.sourceforge.net that is better suited for this.

On Tue May 18 2010 Barak A. Pearlmutter wrote:
> I've tried to do some minor BBDB hacking, mainly just maintenance to
> keep the Debian package working, and have my current version in
>  http://github.com/barak/BBDB
> but it sounds like what you've done is the right thing.

Thank you. -- I'll take a look at this page. Possibly some of your
patches might be obsolete for my version.

> Unless you object, I'll put your version on a branch in that repo.
> This would be easier if you were to tell me which exact point you
> branched off from.

That's fine with me.

I already discovered some minor bugs in the version that I posted on
gnu-emacs-sources and I am sure there will be more. It will probably
be best to put my code in some openly accessible version control
system. (I do not know anything about such systems. I am a happy
user of RCS for my small projects.)

I have contacted the current official maintainer of BBDB. But up to
now I did not get any response.

> Also: care to try for a merge?  It sounds like your version would be
> more suitable for the Debian bbdb package; does that sound right
> to you?

Re: BBDB or BADB (born again database)

"Roland Winkler" <Roland.Winkler <at> physik.uni-erlangen.de> writes:

> I thought I can post this here.
>
> Is this BBDB or BADB (the born-again database)? I don't know!
>
> BBDB had been dormant for quite some time. Actually, I never used it.
> When I looked at it, the code appeared rather rusted to me,
> a software package that had grown organically over many years
> (many years ago), making it difficult to make new changes to it. Yet at
> some point I thought I needed something of that kind to keep track of
> names, phone numbers, email and snail mail addresses and what else.

On a sidenote, did you look at addressbook.el ?
It is work in progress, but the interesting thing is that the author is
positive about inclusion in emacs, and that it uses standard vcards for
contact information.

> When I tried to get BBDB working for me, I ended up doing much more
> changes than I had ever expected. 
>
> - I didn't try to keep any backward compatibility (beyond the latest
>   GNU Emacs released a few days ago), nor did I try to keep the code
>   compatible with Xemacs (which I don't know / don't use). (Yet I
>   could even imagine that it is not so difficult to port the new code.)
>
> - I gave up to write a ChangeLog, changes were too numerous.
>
> - I tried to give variables and functions more consistent names. If
>   you have any old customizations of BBDB, most likely they will not