[bug #59674] Stack on Status Bar Does Not Change Radix

2020-12-14 Thread Anton Ertl
Follow-up Comment #4, bug #59674 (project gforth): Yes, we should do it in "smart.". ~~ calls ..., and it should not matter whether the run-time happens to be in hex or decimal. Yes, we do not know what it is, and therefore guess it, but making the guess on BASE does not appear to be a good

[bug #59674] Stack on Status Bar Does Not Change Radix

2020-12-14 Thread Bernd Paysan
Follow-up Comment #3, bug #59674 (project gforth): We don't know what kind of number something we didn't identify actually is (ASCII code? Bitmask? Count of something?). Therefore, smart. falls back to . if it doesn't know. . is printed in the current base. The user probably knows. I think

[bug #59674] Stack on Status Bar Does Not Change Radix

2020-12-14 Thread Anton Ertl
Follow-up Comment #2, bug #59674 (project gforth): The status line (like ...) displays numbers that are (accessible) addresses outside the dictionary in hex with $ prefix (or as strings), and non-address numbers in decimal, by design. It also displays the base unless it is decimal. I agree that

[bug #57340] ekey goes into strange mode when reading shift-backspace

2020-12-14 Thread Bernd Paysan
Update of bug #57340 (project gforth): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #59674] Stack on Status Bar Does Not Change Radix

2020-12-14 Thread Bernd Paysan
Update of bug #59674 (project gforth): Status:None => In Progress Assigned to:None => paysan ___ Follow-up Comment #1: At the moment, this