Re: bug in field-string and field-string-no-properties

[John Paul Wallington]

> There appears to be a bug in field-string and 
> field-string-no-properties.  When (point) or the POS argument is at 
> the first character of a field, the function returns an empty string. 
> The following fragment of code, executed in the scratch buffer, 
> illustrates the problem.
> 
> (progn
>    (set-buffer (get-buffer-create "junk"))
>    (erase-buffer)
>    (insert "Test")
>    (put-text-property (point-min) (point-max) 'field 1)
>    (message "field-string at 1 = '%s'\nfield-string at 2 = '%s'"
>    (field-string-no-properties 1) (field-string-no-properties 2)))

>From (elisp) Fields Info node:

"When the characters before and after POS are part of the same field,
there is no doubt which field contains POS: the one those characters
both belong to.  When POS is at a boundary between fields, which field
it belongs to depends on the stickiness of the `field' properties of
the two surrounding characters (see *note Sticky Properties::).  The field
whose property would be inherited by text inserted at POS is the field
that contains POS."