Send Ebib-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/ebib-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ebib-users digest..."
Today's Topics:
1. Re: a patch for ebib (Joost Kremers)
2. Re: Ebib 1.5.2 released; git repository (Thomas A. Schmitz)
3. Re: Ebib 1.5.2 released; git repository (Joost Kremers)
4. Re: Ebib 1.5.2 released; git repository (Joost Kremers)
5. Re: Ebib 1.5.2 released; git repository (Thomas A. Schmitz)
6. Re: Ebib 1.5.2 released; git repository (Joost Kremers)
7. Re: Ebib 1.5.2 released; git repository (Thomas A. Schmitz)
----------------------------------------------------------------------
Message: 1
Date: Wed, 31 Oct 2007 20:50:43 +0100
From: Joost Kremers <[EMAIL PROTECTED]>
Subject: Re: [Ebib-users] a patch for ebib
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
On Wed, Oct 31, 2007 at 07:32:57AM +0000, Leo wrote:
> (when (file-readable-p "~/.ebibrc")
> (load "~/.ebibrc"))
>
> may be simplified as:
>
> (load "~/.ebibrc" t)
thanks, i didn't know that.
--
Joost Kremers
Life has its moments
------------------------------
Message: 2
Date: Fri, 2 Nov 2007 15:17:12 +0100
From: "Thomas A. Schmitz" <[EMAIL PROTECTED]>
Subject: Re: [Ebib-users] Ebib 1.5.2 released; git repository
To: "Discussion of issues relating to Ebib."
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Hi Joost,
first: thanks so much. I absolutely love the new release. The manual
looks gorgeous, virtual databases are fabulous, and the possibility to
customize the latex cite commands is wonderful for me (I use ConTeXt
and need a somewhat different style). I use ebib regularly to insert
references into my TeX files; it is the most convenient and fastest
thing out there.
I'm still not quite happy with its editing functionalities. Using it
on a quite big database (more than 1000 entries), two things struck
me; one is inconvenient, the other a bug, I think:
1. When ebib has trouble parsing a database, it simply gives up - no
error code, no hint, it just sits there. Is it feasible to provide
some sort of feedback that something went wrong? I'm not asking for
helpful error codes (I'm aware that this would demand lots of work),
but at least some message would be nice.
2. ebib is very sensitive to unbalanced braces in any field. Some of
my entries contain words in Greek Beta code. Here is an example:
@Article{ harderzwei,
annote = {Examen de l'antith{\`e}se du distique c{\'e}l{\`e}bre:
EIMI D EGW... E)PISTA/MENOS.},
author = {Harder, Richard},
journal = {Hermes},
pages = {381--384},
title = {Zwei Zeilen von Archilochos},
volume = 80,
year = 1952
}
ebib chokes on the unbalanced closing parenthesis in line 3; but its
behavior is dangerous: it just stops parsing the entry at this point
and quietly forgets the rest. When I save the database in ebib, I get
this:
@article{harderzwei,
annote = {Examen de l'antith{\`e}se du distique c{\'e}l{\`e}bre: EIMI
D EGW... E)PISTA/MENOS.
}
After which my database is of course broken for this entry. Can this
be fixed?
Thanks for your great work, and best wishes
Thomas
On Oct 22, 2007, at 10:52 PM, Joost Kremers wrote:
> Hi all,
>
> I've just uploaded Ebib version 1.5.2 to the Sourceforge servers. New
> features in this version:
>
> - Ebib now allows multiple bib-files in the \bibliography command of a
> LaTeX file. (I never knew BibTeX allows this...)
>
> - It is now possible to push entries from the index buffer to a LaTeX
> buffer. With the key 'p', you're asked for a buffer, after which the
> current entry is added to this buffer, together with a cite-
> command. (The
> cite commands used are the same ones used for ebib-insert-bibtex-
> key. The
> default is \cite{<key>}.) The default buffer to push entries to is
> the
> one you called Ebib from.
>
> Note: the key 'p' used to edit the @preamble. It seemed to make more
> sense to use it for pushing entries instead. The preamble can now be
> edited with 'r'.
>
> - If you've put a value in the crossref field of an entry, Ebib now
> shows
> which values the entry inherits from the cross-referenced entty.
>
> - The multiline edit buffer produces a warning when there are
> unbalanced
> braces in the text.
>
> - Ebib now has an option to gracefully handle multiple identical
> fields in
> BibTeX entries (i.e. multiple 'keywords' fields).
>
> I've set up a public git repository for Ebib at
> <http://repo.or.cz/w/ebib.git>. If you want, you can get the latest
> sources
> from there.
>
> Have fun!
>
> Joost
>
>
>
> --
> Joost Kremers
> Life has its moments
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Ebib-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ebib-users
------------------------------
Message: 3
Date: Fri, 2 Nov 2007 18:21:38 +0100
From: Joost Kremers <[EMAIL PROTECTED]>
Subject: Re: [Ebib-users] Ebib 1.5.2 released; git repository
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
hi thomas,
> first: thanks so much. I absolutely love the new release. The manual
> looks gorgeous, virtual databases are fabulous, and the possibility to
> customize the latex cite commands is wonderful for me (I use ConTeXt
> and need a somewhat different style). I use ebib regularly to insert
> references into my TeX files; it is the most convenient and fastest
> thing out there.
thanks. :-)
> I'm still not quite happy with its editing functionalities. Using it
> on a quite big database (more than 1000 entries), two things struck
> me; one is inconvenient, the other a bug, I think:
>
> 1. When ebib has trouble parsing a database, it simply gives up - no
> error code, no hint, it just sits there. Is it feasible to provide
> some sort of feedback that something went wrong? I'm not asking for
> helpful error codes (I'm aware that this would demand lots of work),
> but at least some message would be nice.
that shouldn't be impossible to do, of course. i'll see to what extent it's
possible to add some failure messages to the current code.
in the end, though, i suspect the file-reading code should be rewritten,
allowing for more self-checks and more warning/error messages to the user.
> 2. ebib is very sensitive to unbalanced braces in any field. Some of
> my entries contain words in Greek Beta code. Here is an example:
>
> @Article{ harderzwei,
> annote = {Examen de l'antith{\`e}se du distique c{\'e}l{\`e}bre:
> EIMI D EGW... E)PISTA/MENOS.},
> author = {Harder, Richard},
> journal = {Hermes},
> pages = {381--384},
> title = {Zwei Zeilen von Archilochos},
> volume = 80,
> year = 1952
> }
>
> ebib chokes on the unbalanced closing parenthesis in line 3; but its
> behavior is dangerous: it just stops parsing the entry at this point
> and quietly forgets the rest. When I save the database in ebib, I get
> this:
oops... i should have thought about that... i actually ran into this
problem myself once, but that was on a (multiline) field i created with
ebib, and i solved it by checking for unbalanced parentheses when
*creating* multiline fields. but for existing .bib-files, that's pointless,
of course.
what i *should* have done is to make ebib not choke on unbalanced
parentheses. the simplest way to do that is to tell ebib that () are not to
be considered parentheses at all.
unfortunately, bibtex itself makes this simple solution unnecessarily
difficult, because it actually *allows* braces to be used to enclose an
entry. that is, this:
@article(key,
...
)
is equivalent to:
@article{key,
...
}
but there is probably a way to work around that. with a bit of luck, i'll
have something put together in a few days. i'll let you know when i do.
best,
joost
--
Joost Kremers
Life has its moments
------------------------------
Message: 4
Date: Sat, 3 Nov 2007 12:05:34 +0100
From: Joost Kremers <[EMAIL PROTECTED]>
Subject: Re: [Ebib-users] Ebib 1.5.2 released; git repository
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
hi thomas,
On Fri, Nov 02, 2007 at 06:21:38PM +0100, Joost Kremers wrote:
[unbalanced parentheses in field values]
> what i *should* have done is to make ebib not choke on unbalanced
> parentheses. the simplest way to do that is to tell ebib that () are not to
> be considered parentheses at all.
>
> unfortunately, bibtex itself makes this simple solution unnecessarily
> difficult, because it actually *allows* braces to be used to enclose an
> entry. that is, this:
>
> @article(key,
> ...
> )
>
> is equivalent to:
>
> @article{key,
> ...
> }
>
> but there is probably a way to work around that. with a bit of luck, i'll
> have something put together in a few days. i'll let you know when i do.
well, i've looked at it, and working around this problem isn't so easy as i
had hoped. i have a fix that allows you to use unbalanced parentheses in
field values, but it breaks the ability to use parentheses as entry
delimiter.
so, for that reason, i'm not adding this code to the master branch for
now. but i've added it to the devel branch (ATM, the difference between
master and devel is *only* this code), so that you at least have a way to
load your .bib files, provided you use braces {} to delimit entries.
if you have git installed, you can get the code here:
<http://repo.or.cz/w/ebib.git> (make sure to check out the devel branch, of
course.) if you don't have git, just let me know, i can send you the source
privately.
i haven't looked at error reporting at all yet. from the looks of it, this
parentheses problem cannot be solved within the existing code, so i think
my energy is better spent working on a reimplementation of the .bib-file
parsing code rather than continue to modify the existing code...
--
Joost Kremers
Life has its moments
------------------------------
Message: 5
Date: Sat, 3 Nov 2007 17:40:17 +0100
From: "Thomas A. Schmitz" <[EMAIL PROTECTED]>
Subject: Re: [Ebib-users] Ebib 1.5.2 released; git repository
To: "Discussion of issues relating to Ebib."
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Hi Joost,
thanks for your incredibly fast reaction - this is just great!
On Nov 3, 2007, at 12:05 PM, Joost Kremers wrote:
> hi thomas,
>
> On Fri, Nov 02, 2007 at 06:21:38PM +0100, Joost Kremers wrote:
> [unbalanced parentheses in field values]
>> what i *should* have done is to make ebib not choke on unbalanced
>> parentheses. the simplest way to do that is to tell ebib that ()
>> are not to
>> be considered parentheses at all.
>>
>> unfortunately, bibtex itself makes this simple solution unnecessarily
>> difficult, because it actually *allows* braces to be used to
>> enclose an
>> entry. that is, this:
>>
>> @article(key,
>> ...
>> )
>>
>> is equivalent to:
>>
>> @article{key,
>> ...
>> }
>>
>> but there is probably a way to work around that. with a bit of
>> luck, i'll
>> have something put together in a few days. i'll let you know when i
>> do.
>
> well, i've looked at it, and working around this problem isn't so
> easy as i
> had hoped. i have a fix that allows you to use unbalanced
> parentheses in
> field values, but it breaks the ability to use parentheses as entry
> delimiter.
>
> so, for that reason, i'm not adding this code to the master branch for
> now. but i've added it to the devel branch (ATM, the difference
> between
> master and devel is *only* this code), so that you at least have a
> way to
> load your .bib files, provided you use braces {} to delimit entries.
>
> if you have git installed, you can get the code here:
> <http://repo.or.cz/w/ebib.git> (make sure to check out the devel
> branch, of
> course.) if you don't have git, just let me know, i can send you the
> source
> privately.
>
Sigh... I can see why BibTeX syntax must be giving you headaches. I
knew that you could use either braces or quotation marks as
delimiters, I had no idea that parentheses are possible as well. In
which case it is of course quite difficult for you to make a
universally valid parser. I don't have that much experience with
BibTex databases, but am just wondering how many people actually use
parentheses for this purpose?
> i haven't looked at error reporting at all yet. from the looks of
> it, this
> parentheses problem cannot be solved within the existing code, so i
> think
> my energy is better spent working on a reimplementation of the .bib-
> file
> parsing code rather than continue to modify the existing code...
>
>
Well, maybe a good error-reporting tool would provide a solution. If
ebib could provide something like "There are unbalanced parentheses in
your file on lines X, XX, and XXX. Do you want to edit the file before
I load it" and then load the file into a normal emacs buffer, that
would help. In my case, I have such parentheses in the "annote"-field
only, but of course, I could imagine that they may be found in titles
as well (just think of the old-fashioned German way of haveing
something like "1)" as a numbering system). So I would say disregard
the problem; I'll just have to be careful to edit my files
accordingly. I'll have a look at the other bibtex tools I use (such as
pybliographer, jabref, and bibdesk); they never complained about the
parentheses, so I assume that they disable parentheses as delimiters
for bibtex by default.
I don't have git; could you send me the source file by mail? Thanks a
lot!
All best
Thomas
------------------------------
Message: 6
Date: Tue, 6 Nov 2007 22:28:38 +0100
From: Joost Kremers <[EMAIL PROTECTED]>
Subject: Re: [Ebib-users] Ebib 1.5.2 released; git repository
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
hi thomas,
following up to the other problem you mentioned, about error messages:
> 1. When ebib has trouble parsing a database, it simply gives up - no
> error code, no hint, it just sits there. Is it feasible to provide
> some sort of feedback that something went wrong? I'm not asking for
> helpful error codes (I'm aware that this would demand lots of work),
> but at least some message would be nice.
could you give an example of a .bib file that ebib has trouble with? that
might give me a better idea of what i can do to make ebib more informative
in such cases.
--
Joost Kremers
Life has its moments
------------------------------
Message: 7
Date: Tue, 6 Nov 2007 22:49:51 +0100
From: "Thomas A. Schmitz" <[EMAIL PROTECTED]>
Subject: Re: [Ebib-users] Ebib 1.5.2 released; git repository
To: "Discussion of issues relating to Ebib."
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
On Nov 6, 2007, at 10:28 PM, Joost Kremers wrote:
> could you give an example of a .bib file that ebib has trouble with?
> that
> might give me a better idea of what i can do to make ebib more
> informative
> in such cases.
Hi Joost and all,
will try and cook up a minimal example, but I won't be able to do so
before the end of the week - too many stupid meetings...
All best
Thomas
------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
------------------------------
_______________________________________________
Ebib-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ebib-users
End of Ebib-users Digest, Vol 9, Issue 1
****************************************
