PLEASE IGNORE PREVIOUS EMAIL/POST. treat this as a
replacement. apologies for the noise.

Protesilaos Stavrou <info@protesilaos.com> writes:

> Hyphens were a bug. I pushed commit e200ff9 to cover that case.

e200ff9 now seems to sluggify hyphens in SIGNATURE in a manner which is
consistent with TITLE. and fontification on the sluggified result
works. however, there are still some issues. i'll note these below for
your reference, but assuming you consider them issues as well, the way
to solve these may be to add some tests which do some exhaustive
checking of invariances that ought to exist.

Protesilaos Stavrou <info@protesilaos.com> writes:

> Hyphens were a bug. I pushed commit e200ff9 to cover that case.

e200ff9 now seems to sluggify hyphens in SIGNATURE in a manner which is
consistent with TITLE. and fontification on the sluggified result
works. however, there are still some issues. i'll note these below for
your reference, but assuming you consider them issues as well, the way
to solve these may be to add some tests which do some exhaustive
checking of invariances that ought to exist.

- commas entered in SIGNATURE and TITLE interactive prompts are retained
  in generated filename, however, fontification is broken once again.

Protesilaos Stavrou <info@protesilaos.com> writes:

>>> the current denote-rename-file interface allows the inclusion of
>>> commas, spaces and hyphens - all of which break the fontification in
>>> dired.
>
> I just pushed the changes. Please let me know how they work for you.

for reference, the comments below are from 85d34f0 checkout.

spaces in signature now get converted to "=" as intended and commas in
SIGNATURE get treated in a way that doesn't break fontification (more on
that later). however, hyphens are allowed in SIGNATURE (which is
consistent with TITLE and KEYWORDS), however it breaks fontification in

Protesilaos Stavrou <info@protesilaos.com> writes:

> the 'denote-rename-file' now prompts for a signature

thank you!

on a related note, it seems as if denote-excluded-punctuation-regexp may
not be being consulted during signature entry? the current
denote-rename-file interface allows the inclusion of commas, spaces and
hyphens - all of which break the fontification in dired.

-- 
Suhail

Protesilaos Stavrou <info@protesilaos.com> writes:

> There currently is no way to do this. I am happy to add it.

thank you! that would be helpful. for a collection of research papers
the signature field is a good fit for including author names and the
keywords for encoding categorical labels.

> Checking the denote-prompts will not work at all times. The template and
> subdirectory prompts will not do the right thing.

subdirectory and template don't seem to be inputs to denote-rename-file,
so i'm not sure i follow. my proposal was simply to check whether or not
'signature is a member of denote-prompts and if so prompt signature. if

When renaming binary files via denote-rename-file what is the way to
prompt for signature?

It seems that this isn't currently supported. I'm unfamiliar with the
library, but based on a quick reading of the manual it seems that the
value of denote-prompts should probably be checked to decide whether or
not to prompt for a signature (over and above retrieving the value from
the file front-matter if present).
-- 
Suhail