Generate regular expression matching one character from a set

Hi,

the `regexp-char' function provided below builds a regular
expression string for matching one character from a given
set.  See the 'Commentary' section, for more details.

--

-- 
Ralph Schleicher

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

full-ack 0.1 -- a front-end for ack

full-ack is (yet another) front-end for ack.

From the instruction:
Run `ack' to search for all files and `ack-same' to search for files of the
same type as the current buffer.

`next-error' and `previous-error' can be used to jump to the matches.

The latest version is always available at:
http://nschum.de/src/emacs/full-ack/

regards,
Nikolaj Schumacher

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

recent-addresses 0.1 -- store and recall recently used email addresses

recent-addresses allows you to quickly look up previously used
addresses.

The latest version is always available at:
http://nschum.de/src/emacs/recent-addresses/

regards,
Nikolaj Schumacher

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

company 0.2.1 -- extensible inline text completion mechanism

Company is a modular completion mechanism.

Version 0.2.1 improves elisp completion und includes some minor fixes
and improvements.

It is available at:
http://nschum.de/src/emacs/company-mode/

regards,
Nikolaj Schumacher

full-ack 0.2 -- a front-end for ack

This version contains a few fixes and new methods for using ack to find
the files in the project.

It's available at:
http://nschum.de/src/emacs/full-ack/

regards,
Nikolaj Schumacher

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

Re: company 0.2.1 -- extensible inline text completion mechanism

Nikolaj Schumacher <me <at> nschum.de> writes:

> Company is a modular completion mechanism.
>
> Version 0.2.1 improves elisp completion und includes some minor fixes
> and improvements.
>
> It is available at:
> http://nschum.de/src/emacs/company-mode/
>
>
> regards,
> Nikolaj Schumacher
>
>

How do you see this competing with auto-complete which completes pretty
much anything?

http://www.emacswiki.org/emacs/AutoComplete

Re: company 0.2.1 -- extensible inline text completion mechanism

Richard Riley <rileyrgdev <at> googlemail.com> wrote:

> How do you see this competing with auto-complete which completes pretty
> much anything?

Like auto-complete, this is a front-end.
You can probably bend back-ends for either to work in the other.  In
fact company mode is designed for self-contained exchangable back-ends.

So the question really isn't which one can complete "more".

I consider some of the back-ends in company to be more sophisticated
than what I've seen in auto-complete (Emacs Lisp, CSS, ...), though.  I
certainly wouldn't mind working on back-end compatibility.

It is unfortunate that there now are two packages out there doing mostly
the same thing.  Most of my work on company predates auto-complete
significantly, but I didn't have the time to work on it for a while.
Too bad that was reason enough for someone to duplicate the work.

regards,
Nikolaj Schumacher

Re: company 0.2.1 -- extensible inline text completion mechanism

On 6 abr, 15:54, Nikolaj Schumacher <m... <at> nschum.de> wrote:
> Richard Riley <rileyrg... <at> googlemail.com> wrote:
> > How do you see this competing with auto-complete which completes pretty
> > much anything?
>
> Like auto-complete, this is a front-end.
> You can probably bend back-ends for either to work in the other.  In
> fact company mode is designed for self-contained exchangable back-ends.
>
> So the question really isn't which one can complete "more".
>
> I consider some of the back-ends in company to be more sophisticated
> than what I've seen in auto-complete (Emacs Lisp, CSS, ...), though.  I
> certainly wouldn't mind working on back-end compatibility.
>
> It is unfortunate that there now are two packages out there doing mostly
> the same thing.  Most of my work on company predates auto-complete
> significantly, but I didn't have the time to work on it for a while.
> Too bad that was reason enough for someone to duplicate the work.
>
> regards,
> Nikolaj Schumacher

At first sight, his version for completing elisp (perhaps his version
uses only the current buffer and not the internal lists?) is much
faster, but I really liked that yours allow the user to isearch on the
results and then show only those that matched. You guys should talk :)

OTOH, none of those seems to provide a function like completing-read
that I could use in my libraries...

Re: company 0.2.1 -- extensible inline text completion mechanism

Toby Cubitt <toby-dated-1239518798.058347 <at> dr-qubit.org> wrote:

> There's also Completion-UI (which I believe is also quite a bit older than
> both the others, though I could be wrong).

Not that much.  If you remember, I submitted a patch for one of the
earlier versions, right before I worked on company.  The reason was that
I came up with the overlay-based tooltip, because regular tooltips were
(are) too slow on my system.  At that time CompletionUI didn't seem
stable (and fast)  enough for the amount of stuff I wanted to change.

> The Completion-UI completion sources (or "back-ends") are also fully
> modular, and Henry Weller has sent me code that hooks company-mode
> back-ends into Completion-UI, which I will include in the next release.

Great.  I guess that proves I did a good job at the interface.  ;)

I would love to have a standardized interface, though.  That would be a
good place to start.

regards,
Nikolaj Schumacher

Re: company 0.2.1 -- extensible inline text completion mechanism

Nikolaj Schumacher wrote:
> Richard Riley <rileyrgdev <at> googlemail.com> wrote:
> 
>> How do you see this competing with auto-complete which completes pretty
>> much anything?
> 
> Like auto-complete, this is a front-end.
> You can probably bend back-ends for either to work in the other.  In
> fact company mode is designed for self-contained exchangable back-ends.
> 
> So the question really isn't which one can complete "more".
> 
> I consider some of the back-ends in company to be more sophisticated
> than what I've seen in auto-complete (Emacs Lisp, CSS, ...), though.  I
> certainly wouldn't mind working on back-end compatibility.
> 
> It is unfortunate that there now are two packages out there doing mostly
> the same thing.

Three :)

There's also Completion-UI (which I believe is also quite a bit older than
both the others, though I could be wrong). It's more sophisticated than
auto-complete, and implements many more user-interfaces and features for
in-buffer completion. However, it *doesn't* implement the overlay-based
simulation of tooltips used in auto-complete.

Since Completion-UI is fully modular, new user-interfaces can very easily
be plugged into it, so my intention is to add the auto-completion
interface to Completion-UI, but I haven't had time yet. (Anyone want to