From: "Mattias Engdegård" <mattiase@acm.org>
To: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"43764@debbugs.gnu.org" <43764@debbugs.gnu.org>
Subject: bug#43764: Calc shift right broken
Date: Sat, 10 Oct 2020 18:24:39 +0200 [thread overview]
Message-ID: <AFD5691D-3B86-4B5C-98EB-619135B108B2@acm.org> (raw)
In-Reply-To: <PR3PR06MB6843D55F5B94F69C50AA1F6284080@PR3PR06MB6843.eurprd06.prod.outlook.com>
9 okt. 2020 kl. 17.34 skrev Vincent Belaïche <vincent.b.1@hotmail.fr>:
> What could be improved would be to add some more functions, like (some ideas) :
> • set bit width 0 would remove the automatic clipping meaning infinite width.
This seems both useful and straightforward to implement and understand. I've attached a patch (lacking documentation but otherwise complete) -- is it what you had in mind?
> • have the H prefix (Hyperbolic) not only for 'b l' but also for the other shifts operation, so that the width can be set on an operation by operation basis with the prefix argument.
Your wish has been granted! It already works that way, it's just not very well documented. Try it.
> • Maybe there could be some display mode in which when integers are wider that the bit width this is displayed somehow, e.g. the pipe in 16#12|34 would appear with a bit width of 8, 16#123|4 for a bit width of 7. Just to warn the user « beware the clip ».
It's not a bad suggestion, but since this is Calc, nothing is very simple. Let's give it some thought.
next prev parent reply other threads:[~2020-10-10 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 15:28 bug#43764: Calc shift right broken Vincent Belaïche
2020-10-02 20:49 ` Mattias Engdegård
2020-10-05 8:12 ` Lars Ingebrigtsen
2020-10-05 10:34 ` Mattias Engdegård
2020-10-06 1:28 ` Lars Ingebrigtsen
2020-10-08 12:24 ` Mattias Engdegård
2020-10-09 15:29 ` Mattias Engdegård
2020-10-09 15:34 ` Vincent Belaïche
2020-10-10 16:24 ` Mattias Engdegård [this message]
2020-10-10 16:31 ` Mattias Engdegård
2020-10-13 9:56 ` Mattias Engdegård
2020-11-04 11:14 ` Vincent Belaïche
2020-11-04 11:54 ` Mattias Engdegård
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=AFD5691D-3B86-4B5C-98EB-619135B108B2@acm.org \
--to=mattiase@acm.org \
--cc=43764@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=vincent.b.1@hotmail.fr \
/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).