From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 37507@debbugs.gnu.org
Subject: bug#37507: 26.3; Non-number value for `fill-column' causes wrong-type-arg error for `C-h f'
Date: Tue, 24 Sep 2019 13:49:54 -0700 (PDT) [thread overview]
Message-ID: <fc1c7271-c2dc-4ab2-af04-1fbcd8bbf0a0@default> (raw)
In-Reply-To: <85lfudjwt0.fsf@gmail.com>
> > `fill-column' is supposed to have an integer value > 0.
> >
> > But if it has a non-numeric value then other functions
> > can barf, unless they watch out for that.
>
> Shouldn't users just not set it to a non-numeric value then?
Should? Yes.
Just? I don't see why.
> I'm sure you can cause all sort of errors by setting
> things to invalid values.
And?
If this is only about users setting the value
then the answer is for them to always use
`set-fill-column'. "Should [eom]."
But is there a reason why this shouldn't be protected
here?'
I wonder even whether there is a reason why
`current-column' shouldn't prevent that particular
error by, say, substituting 0 for a `fill-column'
value that's not an integer > 0. I don't propose
that at this point (might break something that
depends on raising an error?), but I wonder if it
wouldn't be reasonable for `current-column' to do.
next prev parent reply other threads:[~2019-09-24 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 18:23 bug#37507: 26.3; Non-number value for `fill-column' causes wrong-type-arg error for `C-h f' Drew Adams
2019-09-24 18:30 ` Drew Adams
2019-09-24 19:53 ` Noam Postavsky
2019-09-24 20:49 ` Drew Adams [this message]
2019-09-25 6:37 ` Eli Zaretskii
2019-10-19 0:35 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc1c7271-c2dc-4ab2-af04-1fbcd8bbf0a0@default \
--to=drew.adams@oracle.com \
--cc=37507@debbugs.gnu.org \
--cc=npostavs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.