ebib-users Mailing List for Ebib (Page 8)
Brought to you by:
joostkremers
Menu
▾
▴
ebib-users — All discussion about Ebib: questions, feature suggestions, problems, etc.
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(14) |
Sep
(5) |
Oct
(9) |
Nov
(4) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
(7) |
Mar
(18) |
Apr
(11) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(12) |
Dec
|
| 2008 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
(3) |
Oct
(7) |
Nov
(2) |
Dec
(7) |
| 2011 |
Jan
|
Feb
|
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(1) |
Sep
(30) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(9) |
Jul
(1) |
Aug
(30) |
Sep
(10) |
Oct
(4) |
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(2) |
Feb
|
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(3) |
Aug
|
Sep
(10) |
Oct
(5) |
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Massimo L. <lau...@gm...> - 2010-04-07 20:44:24
|
Long lines are not wrapped, and are sent out the screen, because they are truncated. This is a different phenomena, I tried with a clean (no init no site) emacs launch and it still occurs. Notice that I also have truncated lines when such lines are longer that the window. My problem is with bibtex files which have hardcoded newline (i.e. multiline fields) in fields that are shown in the index. Since next/prev-entry move the cursor by the use of forward/backward-line, index entries of more than one line mess everything up. This behaviour can be reproduced with the following .emacs and test.bib .emacs contains only the customization of ebib-index-display-fields I tried with both ebib.el from 1.8.0 and git repository. -- Massimo Lauria |
|
From: Joost K. <joo...@fa...> - 2010-04-07 19:26:19
|
On Wed, Apr 07, 2010 at 04:33:32PM +0200, Massimo Lauria wrote: > I have an issue with ebib. I set up the Index Display Fields > to show > Year; Author; Title. > > Sometimes these fields are multiline (notice that i've no full control > of all .bib files). > This results in some entries to span several lines in the index buffer. Mmm... This shouldn't really be happening... The index buffer uses ebib-index-mode, which sets the variable truncate-lines to t. That should cause lines that are too long for the window to be truncated rather than to be wrapped. > This produces two bugs: > - (minor) only one line of the entry is highlighted > - (major) > when I move up/down or using whatever keys trigger ebib-prev/next-entry, > the prev/next entry is correctly shown in the Entry buffer, but the > cursor only moves one line up/down. > Since there are entries spanning more than one line, this completely > disconnect position in the database with the > cursor position in the index buffer. This is ever weirder, because even if lines are too long for the window and are wrapped, Emacs should treat the wrapped line as a single line, so that moving the cursor down on such a line should actually move two screen lines... Try starting Emacs with the -Q option and then load ebib by hand (with M-x load-file RET /path/to/ebib.el RET followed by M-x ebib) and see if the problem still occurs. If not, then I suspect you have some setting that conflicts with truncate-lines. If that is the case, check if you have any word-wrap-related settings in your ~/.emacs, or send me your ~/.emacs so I can take a look. (BTW, 'emacs -Q' doesn't load ~/.emacs, so you'll have to customize Index Display Fields in the Emacs session before you can test it.) Joost -- Joost Kremers Life has its moments |
|
From: Massimo L. <lau...@gm...> - 2010-04-07 14:33:39
|
Hi guy,
I have an issue with ebib. I set up the Index Display Fields
to show
Year; Author; Title.
Sometimes these fields are multiline (notice that i've no full control
of all .bib files).
This results in some entries to span several lines in the index buffer.
This produces two bugs:
- (minor) only one line of the entry is highlighted
- (major)
when I move up/down or using whatever keys trigger ebib-prev/next-entry,
the prev/next entry is correctly shown in the Entry buffer, but the
cursor only moves one line up/down.
Since there are entries spanning more than one line, this completely
disconnect position in the database with the
cursor position in the index buffer.
The following is a dirty hack workaround which print only the first
line of a multiline field in the index entries.
(defun ebib-display-entry (entry-key)
"Displays ENTRY-KEY in the index buffer at POINT."
(set-buffer ebib-index-buffer)
(insert (format "%-30s %s\n"
entry-key
(if ebib-index-display-fields
(let ((cur-entry-hash (ebib-retrieve-entry entry-key ebib-cur-db)))
(mapconcat #'(lambda (field)
(or
(to-raw (let (
(str (gethash field cur-entry-hash))
)
(if (multiline-p str)
(first-line str)
str
))
)
""))
ebib-index-display-fields
"; "))
""))))
The correct solution maybe using something different that
(forward-line -1/+1) in ebib-prev/next-entry:
something like searching backward/forward for the first line beginning
with the new displayed entry.
Another less robust solution is to search backward/forward for a line
beginning with a character, because all lines
of fields displayed in the index buffer are indented.
Thank you
--
Massimo Lauria
|
|
From: Joost K. <joo...@fa...> - 2009-11-25 09:10:52
|
On Wed, Nov 25, 2009 at 12:01:36PM +0800, bin dong wrote:
> Hi all,
> ebib is wonerdfull!
Thanks. ;-)
> But when i want to print my data base, i found it put
> "key (type)" at texttt{} for each tab entry. i wonder how can i
> choose
> field like title of each entry to be printed at texttt{}.
Unfortunately, this isn't possible. The way the entries are printed is
hard-coded in Ebib, it's not really customizable. I also don't see an easy way
to make it customizable, I'd have to think about how best to implement that. The
only thing you could do is to modify the LaTeX file that Ebib creates...
Best,
Joost
--
Joost Kremers
Life has its moments
|
|
From: bin d. <goo...@gm...> - 2009-11-25 04:01:49
|
Hi all,
ebib is wonerdfull!
But when i want to print my data base, i found it put "key (type)"
at texttt{} for each tab entry. i wonder how can i choose
field like title of each entry to be printed at texttt{}.
Thanks a lot!
Bin
---------------------------
Beihang University
|
|
From: Isaac W. <isa...@gm...> - 2008-04-28 15:48:14
|
Joost, Thank you for your reply. The relevant lines from *Messages* are as follows. Loading ebib (compiled; note, source file is newer)... Loading cl-macs...done Loading ebib (compiled; note, source file is newer)...done 1332 entries, 0 @STRINGs and no @PREAMBLE found in file. Mark set Pushed entries to buffer blah.tex Mark set Saving file c:/blah.tex... Wrote c:/blah.tex Database C:/references.bib not loaded The filename in the \bibliography command matches the one above. Isaac On Mon, Apr 28, 2008 at 4:14 AM, Joost Kremers <joo...@fa...> wrote: > (i sent a reply to this message to the list yesterday, but it doesn't seem > to have gotten through. so i'm replying again, sending a CC to the OP.) > > On Sat, Apr 26, 2008 at 11:47:47AM -0700, Isaac Waisberg wrote: > > How do I load the bibliography file from within LaTeX or make sure > > that it is loaded? > > ebib searches the LaTeX file for a \bibliography command and reads the > file > name from its argument. that filename should be identical to the filename > that ebib displays in the modeline of the index buffer. > > could you tell me the exact error message you get from ebib? (check the > *Messages* buffer if it disappears from the minibuffer too quickly.) does > the filename in the \bibliography command match the one in the mode line > of > the index buffer? if not, how are they different? > > > -- > Joost Kremers > Life has its moments > |
|
From: Isaac W. <isa...@gm...> - 2008-04-26 18:47:52
|
I am using Ebib with LaTeX and Emacs 22.2 in Windows XP.
I redefined the insertion strings as follows:
0: {%s}
1: \citet{%s}
2: \citep{%s}
Everything works fine when I push an entry to a LaTeX buffer (using
either M-1 or M-2 and p).
However, when I am working on my LaTeX buffer and try to insert an
entry using ebib-insert-bibtex-key I get a message saying that the
bibliography file is not loaded.
If I do M-x ebib the bibliography file opens properly and seems to be loaded.
How do I load the bibliography file from within LaTeX or make sure
that it is loaded?
Thanks.
Isaac
|
|
From: Leo <sd...@gm...> - 2008-02-08 02:00:59
|
- add autoload candy for `ebib' - (ebib-fill-index-buffer): use mapc instead of mapcar - (ebib-mark-entry): fix a typo |
|
From: Joost K. <joo...@fa...> - 2008-01-29 12:17:51
|
On Mon, Jan 28, 2008 at 11:19:00PM +0100, Morgan Veyret wrote: > Hello, > I'm trying ebib as a replacement for jabref and emacs integration is > really a good idea for bibtex database management ! > I got a question about the index-mode, is it possible to display some > fields values in this mode instead of just the bibtex key? > > Having the title displayed or even some columns you can select would be > great ! it's certainly feasible. i'll look into it and let you know when i have something. (which will certainly be a couple of weeks, as i have little time right now.) -- Joost Kremers Life has its moments |
|
From: Morgan V. <pa...@ap...> - 2008-01-28 22:17:44
|
Hello, I'm trying ebib as a replacement for jabref and emacs integration is really a good idea for bibtex database management ! I got a question about the index-mode, is it possible to display some fields values in this mode instead of just the bibtex key? Having the title displayed or even some columns you can select would be great ! -- Morgan Veyret (ve...@en...) ------------------------------------------------------------------------------ Centre Européen de Réalité Virtuelle (CERV) 25, rue Claude Chappe BP 38 F-29280 Plouzané (France) ------------------------------------------------------------------------------ Tél: +33 (0)2 98 05 89 43 Fax: +33 (0)2 98 05 89 79 http://www.cerv.fr ------------------------------------------------------------------------------ ,'``.._ ,'``. :,--._:)\,:,._,.: All Glory to :`--,'' :`...';\ the HYPNO TOAD! `,' `---' `. / : / \ ,' :\.___,-. `...,---'``````-..._ |: \ ( ) ;: ) \ _,-. `. ( // `' \ : `.// ) ) , ; ,-|`. _,'/ ) ) ,' ,' ( :`.`-..____..=:.-': . _,' ,' `,'\ ``--....-)=' `._, \ ,') _ '``._ _.-/ _ `. (_) / )' ; / \ \`-.' `--( `-:`. `' ___..' _,-' |/ `.) `-. `.`.``-----``--, .' |/`.\`' ,','); ` (/ (/ |
|
From: Marcelo B. <m.t...@gm...> - 2007-11-18 02:23:57
|
hi Joost, as I said I don't know LISP but will take a look, If I get some ideas I just send some patch to the list. Maybe try to check to see if the export field if RAW than check to see if some of the words on those raw fields match with some of the loaded string, if both are true (RAW field + word match) ebib can ask the user if he wants to also export the matched strings. Do you have some other idea ? Some other way to check ? I will take a look into the code, let's see how LISP looks like :) my very thanks for the fast answer ! regards, marcelo bianchi 2007/11/17, Joost Kremers <joo...@fa...>: > hi marcelo, > > > I just started to use ebib and liked it a lot, actually I just started > > to use Emacs and it's very nice. Well, yesterday I was trying to > > organize my bookmarks and than I decided to set all the journals > > reference using a @STRING because I really hate to type the journal > > names, but after some time I decided to split my database into many > > files but when I use the export 'x' key and but I realize that it > > doesn't check to see if the entry made some use of @STRING definitions > > so it copies that definition toguether with the reference right ? > > the export function doesn't check whether the entry or entries being > exported contain @STRING abbreviations. perhaps it should... but it's als= o > possible to export @STRING definitions themselves, so you can use that to > make sure your new .bib files have all the @STRING definitions they need. > > i admit, it's a little cumbersome that way, unless you just export all > @STRING definitions at once (use `X' in the strings buffer for that). i'l= l > see if there's a not too complicated way to check for @STRING abbreviatio= ns > in entries, so they can be exported automatically, if necessary. > > > -- > Joost Kremers > Life has its moments > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Ebib-users mailing list > Ebi...@li... > https://lists.sourceforge.net/lists/listinfo/ebib-users > --=20 Seismology Student, University of S=E3o Paulo/IAG S=E3o Paulo - Brazil - http://www.iag.usp.br/ WebSpace @ http://my.opera.com/m.tchelo/ |
|
From: Joost K. <joo...@fa...> - 2007-11-17 15:59:30
|
hi marcelo, > I just started to use ebib and liked it a lot, actually I just started > to use Emacs and it's very nice. Well, yesterday I was trying to > organize my bookmarks and than I decided to set all the journals > reference using a @STRING because I really hate to type the journal > names, but after some time I decided to split my database into many > files but when I use the export 'x' key and but I realize that it > doesn't check to see if the entry made some use of @STRING definitions > so it copies that definition toguether with the reference right ? the export function doesn't check whether the entry or entries being exported contain @STRING abbreviations. perhaps it should... but it's also possible to export @STRING definitions themselves, so you can use that to make sure your new .bib files have all the @STRING definitions they need. i admit, it's a little cumbersome that way, unless you just export all @STRING definitions at once (use `X' in the strings buffer for that). i'll see if there's a not too complicated way to check for @STRING abbreviations in entries, so they can be exported automatically, if necessary. -- Joost Kremers Life has its moments |
|
From: Marcelo B. <m.t...@gm...> - 2007-11-17 15:42:27
|
Hello Dear Users, I just started to use ebib and liked it a lot, actually I just started to use Emacs and it's very nice. Well, yesterday I was trying to organize my bookmarks and than I decided to set all the journals reference using a @STRING because I really hate to type the journal names, but after some time I decided to split my database into many files but when I use the export 'x' key and but I realize that it doesn't check to see if the entry made some use of @STRING definitions so it copies that definition toguether with the reference right ? Does anyone faced some type of problem like this ? Has anyone thought about code a solution ? I did not know any LISP (yet :)) but maybe we can find a way ! my best regards, marcelo bianchi --=20 Seismology Student, University of S=E3o Paulo/IAG S=E3o Paulo - Brazil - http://www.iag.usp.br/ WebSpace @ http://my.opera.com/m.tchelo/ |
|
From: Joost K. <joo...@fa...> - 2007-11-07 19:34:08
|
On Wed, Nov 07, 2007 at 01:19:45PM -0500, Sharat Chikkerur wrote: > I'm a new user and was having trouble exporting keys to latex files. When > I "push" keys in ebib mode, it opens a new buffer called *(Ebib-edit)* and > inserts the key there instead of the latex buffer. Just wondering what I > was doing wrong. perhaps nothing at all... but i'm not sure what's going on. could you describe in more detail what you're doing? when you push an entry with 'p', you should be asked which buffer you want to push the key to, and ebib shouldn't do anything before you've given the name of a buffer. in the previous ebib version, the key 'p' would start editing the preamble, and that would indeed put you in a buffer called *Ebib-edit* (without the parentheses, however). i don't understand how it's possible that the entry key is inserted there, though. you say you're a new user, so you got the latest release from sourceforge, and don't have any older version lying around, and you also don't have a .ebibrc file in your home directory? -- Joost Kremers Life has its moments |
|
From: Sharat C. <sha...@gm...> - 2007-11-07 18:19:54
|
Hi, I'm a new user and was having trouble exporting keys to latex files. When I "push" keys in ebib mode, it opens a new buffer called *(Ebib-edit)* and inserts the key there instead of the latex buffer. Just wondering what I was doing wrong. regards Sharat On Nov 6, 2007 4:49 PM, Thomas A. Schmitz <tho...@un...> wrote: > > 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 > Ebi...@li... > https://lists.sourceforge.net/lists/listinfo/ebib-users > -- Sharat Chikkerur I'm running for a cause. Support team AID-Asha http://www.teamaidasha.org/Runner2007.aspx?Num=20070026 http://web.mit.edu/sharat/www |
|
From: Joost K. <joo...@fa...> - 2007-11-07 13:37:13
|
Thomas A. Schmitz schrieb: > 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... that'd be great. there's no hurry, i have lots to do myself... best, joost |
|
From: Thomas A. S. <tho...@un...> - 2007-11-06 21:50:13
|
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 |
|
From: Joost K. <joo...@fa...> - 2007-11-06 21:29:27
|
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 |
|
From: Thomas A. S. <tho...@un...> - 2007-11-03 16:40:37
|
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
|
|
From: Joost K. <joo...@fa...> - 2007-11-03 11:06:29
|
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
|
|
From: Joost K. <joo...@fa...> - 2007-11-02 17:22:32
|
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
|
|
From: Thomas A. S. <tho...@un...> - 2007-11-02 14:17:34
|
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
> Ebi...@li...
> https://lists.sourceforge.net/lists/listinfo/ebib-users
|
|
From: Joost K. <joo...@fa...> - 2007-10-31 19:51:34
|
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 |
|
From: Leo <sd...@gm...> - 2007-10-31 07:33:30
|
On 2007-10-29 10:33 +0000, Joost Kremers wrote: > On Mon, Oct 29, 2007 at 06:46:59AM +0000, Leo wrote: >> Hi there, >> >> Fix a typo and a compiler warning and add an autoload candy for `ebib'. > > thanks! i've applied the patch and pushed the new source to > <http://repo.or.cz/w/ebib.git>. > > for some reason, i never got the compiler message you mention, but mapc > does make more sense here than mapcar. Many thanks. BTW, (when (file-readable-p "~/.ebibrc") (load "~/.ebibrc")) may be simplified as: (load "~/.ebibrc" t) Cheers, -- .: Leo :. [ sdl.web AT gmail.com ] .: [ GPG Key: 9283AA3F ] :. Use the most powerful email client -- http://gnus.org/ |
|
From: Joost K. <joo...@fa...> - 2007-10-29 10:34:43
|
On Mon, Oct 29, 2007 at 06:46:59AM +0000, Leo wrote: > Hi there, > > Fix a typo and a compiler warning and add an autoload candy for `ebib'. thanks! i've applied the patch and pushed the new source to <http://repo.or.cz/w/ebib.git>. for some reason, i never got the compiler message you mention, but mapc does make more sense here than mapcar. -- Joost Kremers Life has its moments |
3 messages has been excluded from this view by a project administrator.
