I just tried editing a file that has an FF with a few common editors. It
does not work properly in several of them. In particular in linux textedit
and in JHS codemirror. I would not be able to work with scripts that had FF
in them!
On Sun, Jul 18, 2021 at 6:38 PM Henry Rich wrote:
> In the
In the middle of a line FF would need to be whitespace which would mean
you have to decide how to display it, etc.
Treated as a line-end it is discarded as the file is read, and there are
no further repercussions as the FF is not part of what gets interpreted.
There would be the side effect
Yeah. Or at least that's the only way I've ever seen it used.
It was originally literally to feed a new form into your printer when you
were printing your source code,
so it really doesn't make sense anywhere else.
On Sun, Jul 18, 2021 at 6:22 PM Eric Iverson
wrote:
> Is it used only when
Is it used only when alone on a line? Things get messier when it is allowed
anywhere,
On Sun, Jul 18, 2021 at 6:10 PM Michal Wallace
wrote:
> FF is actually pretty commonly used in source code... I use it all the time
> in python and rust.
> It's actually used as part of the GNU C coding
FF is actually pretty commonly used in source code... I use it all the time
in python and rust.
It's actually used as part of the GNU C coding standard, according to
wikipedia (pretty sure that's where I picked it up...)
https://en.wikipedia.org/wiki/Page_break#Semantic_use
On Sun, Jul 18, 2021
In linux jconsole input ctrl+l, is not treated as LF. Instead it scrolls
down the page.
I think you will find that ctrl+l will behave differently on many different
hosts, terminal managers, J front ends, etc. I think making it behave in a
useful way and the same way in all cases is not possible.
On Sun, Jul 18, 2021 at 4:55 PM chris burke wrote:
> I think FF is normally considered to be whitespace, so it can be treated
> like LF.
Yes.
https://en.wikipedia.org/wiki/Whitespace_character
Thanks,
--
Raul
--
For
Bingo! When reading from a script, the code discards UP TO TWO trailing
control characters at the end of a line. Thus
0!:1 (49 12 13 { a.)
1
1
0!:1 (49 12 13 10 { a.) NB. normal Windows
1♀
|spelling error
| 1♀
| ^
|[-0]
0!:1 (49 12 10 { a.) NB. Normal Linux
1
1
Sound point. To summarize:
* If FF is part of a broader markup language, that markup should be
handled in a preprocessor.
* OTOH, if you use a preprocessor, you can't complain if everyone else
uses one too, and if they are not compatible you have Babel. That is,
calling for a preprocessor
Hrm. I always place it on a blank line by itself, and it does not give a
spelling error on linux in this case.
Could it be that the code for platform-specific line endings ignores any
character c after an LF if 32>a.i.c ?
On Sun, Jul 18, 2021 at 4:55 PM chris burke wrote:
> It looks like FF
What about chars for vertical tab, bell, etc? What is whitespace and what
is an error is a tricky question. I would be against any change in this
area. It has been this way for 30 years.
Fancier scripts (literate programming) are great, but FF is the tip of that
iceberg. I suggest that a script
It looks like FF is not supported in linux scripts, e.g.
9!:14''
j903/j64avx2/linux/beta-l/commercial/
www.jsoftware.com/2021-06-17T13:00:33/clang-10-0-0/SLEEF=1
('1',FF,'2') fwrite 't1.ijs'
3
0!:1 <'t1.ijs'
1
2
|spelling error
| 1
2
|^
|[-0] t1.ijs
I think FF is
Every bytecode that is not an ASCII graphic or SP, CR, TAB, or LF will
cause a spelling error if encountered as a word:
". 12 { a.
|spelling error
|
The question here is whether FF is enough of an industry-standard to be
called whitespace, like TAB.
I don't know myself. I have looked at
More on FF. If there is to be preprocessing of a script to make it suitable
for load, it should be done in J, rather than the front end.
load fix 'test.ijs'
On Sun, Jul 18, 2021 at 3:56 PM Eric Iverson
wrote:
> FF char (12{a.) gets a spelling error if in a script that is loaded in
> linux.
FF char (12{a.) gets a spelling error if in a script that is loaded in
linux. I think this would be the same as in windows but have not tested.
There are lots of values that will give spelling errors. I am not sure it
makes sense to special case (i.e. ignore FF).
If the FF is desired for its
no clue. as far as i know it's just a plain ascii character. as i said, it
works in jqt on windows, too.
On Sun, Jul 18, 2021 at 3:39 PM Henry Rich wrote:
> I will look into turning FF into LF when a script is read, & will do it
> if there are no problems.
>
> Does Linux do something to the FF?
I will look into turning FF into LF when a script is read, & will do it
if there are no problems.
Does Linux do something to the FF? I don't see why you don't get the
same error there as on Windows.
Henry Rich
On 7/18/2021 7:58 AM, Michal Wallace wrote:
I sometimes use the ^L character
I sometimes use the ^L character (FF, or 12{a.) in source code files to
divide my code into "pages".
(I have emacs set up so that I can page back and forth showing one page at
a time without scrolling, so the top line of the page is always at the top
of the screen when that page is showing, etc.)
18 matches
Mail list logo
