Thank you very much Christiaan.
==Tamer
Sent from my mobile, excuse the brevity and typos.
> On May 17, 2023, at 9:37 AM, Christiaan Hofman wrote:
>
> I will add a separate preference option to control whether to overwrite
> existing cite keys.
>
> Christiaan
>
>> On 17 May 2023, at 05:0
I will add a separate preference option to control whether to overwrite
existing cite keys.
Christiaan
> On 17 May 2023, at 05:04, M. Tamer Özsu via Bibdesk-users
> wrote:
>
> Sorry, I missed that question from Christiaan. In my case, I autogenerate the
> cite key, but then want to prefix it
Sorry, I missed that question from Christiaan. In my case, I autogenerate the
cite key, but then want to prefix it with the abbreviation of the name of the
conference or journal where it appeared. The hacky way I do it is to open the
.bib file after I autogenerate the cite key and just prepend t
> On May 16, 2023, at 15:12 , Christiaan Hofman wrote:
>
> Just wondering, why would you not want to auto-generate the cite key when
> adding?
If you have a master .bib file and create smaller ones as needed by
project/report/topic/etc, it makes sense that you'd want the same citekeys in
b
Just wondering, why would you not want to auto-generate the cite key when
adding?
Christiaan
> On 16 May 2023, at 23:51, M. Tamer Özsu via Bibdesk-users
> wrote:
>
> Right. That is what is happening -- open the file, cite keys in the .bib file
> is maintained; but copy those into the master
Right. That is what is happening -- open the file, cite keys in the .bib file
is maintained; but copy those into the master .bib file, they are revised. Now
that I know why, I can work around it.
Many thanks Christiaan.
==Tamer
> On May 16, 2023, at 5:12 PM, Christiaan Hofman wrote:
>
> It d
It doesn’t, and shouldn’t, change it for existing items. Only for new items,
i.e. ones that you add or create.
Christiaan
> On 16 May 2023, at 22:58, Christiaan Hofman wrote:
>
> No, it changed a bit.And it does work, that’s why it changed. It generates
> the cite key for newly added items, a
OK, I'll turn it off while importing the file and then turn it back on.
Interestingly, if I just open that .bib file (with the "icde22_" prefix in the
cite key, it does not change things; only when I copy and add them to my master
.bib file.
==Tamer
> On May 16, 2023, at 4:58 PM, Christiaan H
No, it changed a bit.And it does work, that’s why it changed. It generates the
cite key for newly added items, as the preference choice says.
Christiaan
> On 16 May 2023, at 18:59, M. Tamer Özsu via Bibdesk-users
> wrote:
>
> Yes, Christian, that is the case. It never occurred to me that it c
Yes, Christian, that is the case. It never occurred to me that it could be a
problem; I’ve always had it turned on and it used to work (I think). Perhaps I
was temporarily turning it off previously.
Many thanks.
==Tamer
> On May 16, 2023, at 10:13 AM, Christiaan Hofman wrote:
>
> Do you have
Do you have automatic cite key generation turned on (and is your cite key
format %a1:%Y%u2)?
Christiaan
> On 16 May 2023, at 16:03, M. Tamer Özsu via Bibdesk-users
> wrote:
>
> I have run into an interesting issue with Bibdesk (1.8.16) that I had not
> encountered before. I have a .bib file
I have run into an interesting issue with Bibdesk (1.8.16) that I had not
encountered before. I have a .bib file that has entries like the following. The
relevant part of this is the @inproceedings{icde22_Wang:2022aa line. When I
copy them into my master Bibdesk library, it loses the “icde22_” a
12 matches
Mail list logo
