unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36573@debbugs.gnu.org, rswarbrick@gmail.com
Subject: bug#36573: 26.1; bufferpos-to-filepos assumes coding-system-eol-type gives integer
Date: Thu, 12 Aug 2021 16:08:05 +0300	[thread overview]
Message-ID: <83pmuidd56.fsf@gnu.org> (raw)
In-Reply-To: <878s16n7qc.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  12 Aug 2021 14:54:51 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: rswarbrick@gmail.com,  36573@debbugs.gnu.org
> Date: Thu, 12 Aug 2021 14:54:51 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I think, since these cases are very rare, it should be okay to assume
> > the -unix EOL type when this happens, and document that if this is the
> > case, the result could be an approximation even if the exact result
> > was requested.
> 
> It is a rare odd corner case, but I think erroring out is a better
> solution here than having to document this.  :-)  `exact' meaning
> "exact" is easier conceptually.

Fine with me, but I think we will still need to say in the doc string
something like

  It is an error to request the `exact' method when the buffer's EOL
  format is not yet decided.





  reply	other threads:[~2021-08-12 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 10:52 bug#36573: 26.1; bufferpos-to-filepos assumes coding-system-eol-type gives integer Rupert Swarbrick
2019-07-10 14:52 ` Eli Zaretskii
2019-07-12 15:14 ` Rupert Swarbrick
2019-07-12 18:17   ` Eli Zaretskii
2021-08-11 18:42   ` Lars Ingebrigtsen
2021-08-12  8:21     ` Eli Zaretskii
2021-08-12 12:54       ` Lars Ingebrigtsen
2021-08-12 13:08         ` Eli Zaretskii [this message]
2021-08-13 11:07           ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pmuidd56.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=36573@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rswarbrick@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).