With the CSL gui I try hard to keep the linelength of the windows at 80.
This at least started with concern about what on earth to do when and if
the user resized the windows. There was no good or obvious way to cause
the lisp/reduce core to be informed of a change in linelength and reformat
everything to allow for any change. Equally I did not want or feel like
making a user call to the linelength function to suddenly re-size the
screen. I also was uncomfortable with ending up with output (especially
displayed maths) clipped within a scrollable screen. I end up with making
it such that the menu item that resets the font forces the width of the
windows to be exactlty 80 characters, and attempts to alter the windows
width by dragging corners etc should not do that. I had sort of wanted to
make dragging windows corners to alter size adust the font sizes to keep
things at 80 columns. That I can do with code that is potentially there
for the future but rendering characters at non-whole-number font sizes in
a portable way is not utterly trifling esp when you want to build big
delimiters out of adjacacnt glyphs.
The short issue is that altering the linelength for the main terminal
window in CSL Reduce under its gui is not as effective as you wanted. You
may have more luck if you are sending the generated C to file not to the
screen?
If you wish to work on an alternative behaviour of course all the souce
code is there for you to play with!
What is surprising is that the setting of the terminal line length affects the line length of a file written using gentran. I set gentranout. I do not know if linelength and
clinelen!*:=150;
also interacts in the console mode reduce.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am on a trip at present and can not investigate details until I am home
- and even then I will probably feel that some other issues take priority
unless I find this really trivial, since you have such easy work rounds
and anyway the length of lines if a file mainly destnes to be consumed by
a C compiler not read by humans is something I find it hard to get excited
about!!!! I tried a direct reply to your email that reached us all via
sourceforge but you have not set yoursef up so that that is accepted -
please do so and then remind just me about this again in 2 weeks time.
Arthur
On Thu, 18 Jul 2019, arpi wrote:
More precisely, it works correctly with rfcsl, and not with redcsl, run as
redcsl -w- or redcsl -w+.
Did you set
clinelen!*
after loading gentran? The following works for me:Rainer
Yes, i did so. However, now I tried text mode reduce, and it also worked. Not so in the X GUI of CSL Reduce.
With the CSL gui I try hard to keep the linelength of the windows at 80.
This at least started with concern about what on earth to do when and if
the user resized the windows. There was no good or obvious way to cause
the lisp/reduce core to be informed of a change in linelength and reformat
everything to allow for any change. Equally I did not want or feel like
making a user call to the linelength function to suddenly re-size the
screen. I also was uncomfortable with ending up with output (especially
displayed maths) clipped within a scrollable screen. I end up with making
it such that the menu item that resets the font forces the width of the
windows to be exactlty 80 characters, and attempts to alter the windows
width by dragging corners etc should not do that. I had sort of wanted to
make dragging windows corners to alter size adust the font sizes to keep
things at 80 columns. That I can do with code that is potentially there
for the future but rendering characters at non-whole-number font sizes in
a portable way is not utterly trifling esp when you want to build big
delimiters out of adjacacnt glyphs.
The short issue is that altering the linelength for the main terminal
window in CSL Reduce under its gui is not as effective as you wanted. You
may have more luck if you are sending the generated C to file not to the
screen?
If you wish to work on an alternative behaviour of course all the souce
code is there for you to play with!
Arthur
On Wed, 17 Jul 2019, arpi wrote:
Related
Bugs: #102
What is surprising is that the setting of the terminal line length affects the line length of a file written using gentran. I set gentranout. I do not know if linelength and
clinelen!*:=150;
also interacts in the console mode reduce.
More precisely, it works correctly with rfcsl, and not with redcsl, run as redcsl -w- or redcsl -w+.
I am on a trip at present and can not investigate details until I am home
- and even then I will probably feel that some other issues take priority
unless I find this really trivial, since you have such easy work rounds
and anyway the length of lines if a file mainly destnes to be consumed by
a C compiler not read by humans is something I find it hard to get excited
about!!!! I tried a direct reply to your email that reached us all via
sourceforge but you have not set yoursef up so that that is accepted -
please do so and then remind just me about this again in 2 weeks time.
Arthur
On Thu, 18 Jul 2019, arpi wrote:
Related
Bugs: #102