[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Emacs-diffs] master c4782ea: Improve and extend filepos-to-bufferpo
Re: [Emacs-diffs] master c4782ea: Improve and extend filepos-to-bufferpos
Fri, 19 Jun 2015 09:59:38 +0300
> From: Stefan Monnier <address@hidden>
> Cc: Eli Zaretskii <address@hidden>
> Date: Thu, 18 Jun 2015 23:17:28 -0400
> > + (if (<= byte eol-offset)
> > + (setq pos (point-min))
> > + (setq pos (point-max))))
> Aka (setq pos (if (<= byte eol-offset) (point-min) (point-max)))
Yes, but my code is clearer, IMO.
> > (let ((eol (coding-system-eol-type coding-system))
> > (type (coding-system-type coding-system))
> > + (base (coding-system-base coding-system))
> > (pm (save-restriction (widen) (point-min))))
> > + (and (eq type 'utf-8-emacs)
> > + (setq type 'utf-8))
> (coding-system-type 'utf-8-emacs) returns `utf-8', so how/when can
> `type' be `utf-8-emacs'?
Never. I guess I got confused with coding-system-base.
> > + (and (eq type 'utf-8)
> > + ;; Any post-read/pre-write conversions mean it's not really UTF-8.
> > + (not (null (coding-system-get coding-system
> > :pos-read-conversion)))
> > + (setq type 'not-utf-8))
> I guess this also applies for latin-N and utf-16, IOW for any value of
> `type', right?
Not really, no. UTF-8 is special here, in that we believe we know how
to compute the byte position exactly, which is not true when there are
conversions. Some profoundly non-UTF-8 encodings have that type, but
then apply conversions that make them something very different.
> > + (and (not (eq type 'utf-8))
> > + (eq quality 'exact)
> > + (setq type 'use-exact))
> IIUC this makes us use the slow exact code for latin-N.
Only if they ask for 'exact'.
> Why is it needed?
They asked for it, didn't they?
A more important problem is that we handle type before accuracy, so
when exact is requested, the type checks should be bypassed, except
> > + (`utf-16
> > + ;; Account for BOM, which is always 2 bytes in UTF-16.
> > + (setq byte (- byte 2))
> Should that only be done for utf1-16B-with-signature?
Do we have a UTF-16 encoding without a signature?
> > + ;; In approximate mode, assume all characters are within the
> > + ;; BMP, i.e. take up 2 bytes.
> > + (setq byte (/ byte 2))
> > + (if (= eol 1)
> > + (filepos-to-bufferpos--dos (+ pm byte) #'byte-to-position)
> > + (byte-to-position (+ pm byte))))
> Shouldn't this use `identity' rather than `byte-to-position'?
This code tested OK for me, feel free to change if you have a test