[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

EDB 1.23 available

From: Thien-Thi Nguyen
Subject: EDB 1.23 available
Date: Wed, 08 Sep 2004 15:24:23 +0200


this is another clean-up release, w/ an even mix of bugfixes and small
improvements.  it looks like the skills of a surgeon are not required
for clean-up, thankfully.


README excerpt:

  This directory contains EDB, the Emacs Database.
  EDB was written by Michael Ernst <address@hidden>,
  and is being maintained by Thien-Thi Nguyen <address@hidden>.

NEWS excerpt:

  - 1.23 | 2004-08-29
    - Bugfix: Functions no longer switched via `fset'
        EDB used to fset `save-some-buffers' to `db-save-some-buffers',
        storing the original version away to call later.  Even though
        this was documented, this kind of behavior is now considered a
        misfeature at best.  EDB no longer does this.  The command
        `db-save-some-buffers' is still available, but you have to
        invoke it as `M-x db-save-some-buffers', or bind a key to it.
        Likewise, `insert' was fset to `db-insert', an EDB-internal func.
        [Gratuitous Comment: This one blew my mind when I discovered it.
        Perhaps all the hand-wringing about speed in the source code
        comments would not have been necessary had such a fundamental
        function not been toyed with so capriciously in the first place.
        Che palle!]
    - Bugfix: local variable `enable-multibyte-characters' handled specially
        When writing the database to an external file format, one of
        the steps is to copy local variables from one buffer to another.
        Previously this did not call `set-buffer-multibyte', resulting in
        a "trying to set constant" error.
    - Command dropped: edb-update
        Changes in distribution and build practice have rendered this
        command obsolete.
    - Variable deprecated: db-default-field-type
    - Function takes optional third arg: database-set-fieldnames-to-list
        This pair of changes is explained in some detail in info node
        "(edb)The database structure".  Migration from the former to the
        latter is encouraged but not enforced (for EDB 1.x).
    - Command `dbf-set-summary-format' now allows editing of current value
    - Internal file format now uses `pp'
        This is still EDB "format 0.6" but now it is written using
        `pp' primarily for the its escaping of newlines (as "\n").
        Before, newlines in data fields were output verbatim.
        This should result in greater chance of identifying any data
        corruption occuring during transmission through varying
        eol-policy domains (email, through usloth machines, whatever).
    - Miscellaneous updates and bug fixes in `examples' subdir
    - New reflection/testing in `skram' subdir
        This is work-in-progress.  The idea is to use EDB to track
        changes to EDB.  Version control is one thing, design control is
        another...  Yes, EDB dares to venture into the dreaded land of
        Project Manglement!
        Actually, like all things to do w/ manglement, this demonstrates
        two aspects of EDB having to deal w/ trust: 1/ it is trustworthy
        enough to run scripts or participate in editing sessions where
        its current over-reaching of namespace is tolerable; and 2/ it
        requires manual verification, still, despite 1/.

cvs tag:


tarball, anoncvs instructions, and other files in dir:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]