🚀 go-pugleaf

In article <Cur3x5.A95@world.std.com>,
Joseph H Allen <jhallen@world.std.com> wrote:
>
>                           Joe's Own Editor 1.0.12

The latest version is now 1.0.13: please wait until that appears in the ftp
directory before getting joe.

Version 1.0.13 includes fixes for these bugs:

- A long sequence of searches or a search & replace with a lot of
  replacements would cause the editor to exit and display an 'Out of memory'
  message.

- If you deleted characters on a long line on a terminal which has a delete
  character command, spaces would someimtes be shifted in place of some of
  the characters.

- If you hit SPACE BACKSPACE RETURN on an otherwise empty prompt line, the
  editor would hang.

- If you typeahead a bunch of returns as the editor is starting, they would
  be converted to ^Js by the tty, which is the kill-line function in joe.

- When a backup file is created, any existing file of the same name is first
  deleted.  This fixes a problem when joe is being used for ELM- other
  people's backup files in the /tmp directory would prevent you from saving
  your own file.  This is also useful when root edits a file in some user's
  account.  The user wouldn't then be able to save his file because joe
  couldn't write to root-owned backup file.

Also these improvements to the search & replace system were made:

The wildcard \* now will not cross line boundaries.  This ends up being more
useful.

\+ now tries to make the longest possible match, instead of the shortest. 
This is much more intuitive:

	\[A-Za-z_]\+\[A-Za-z0-9_]  is all that's needed to match C
                                   identifiers.  It used to be:

	\[A-Za-z_]\+[A-Za-z0-9_]\[^A-Za-z0-9_]

\* still makes the shortest possible match though.  \c (like \*- but don't
stop in balanced expressions) should be used in 99% of all cases you needed
\* to make a longed match.

A full set of backslash escape sequnces is now available for search:

	\a, \n, \r, \b, \t, \e, \f

	match ascii: BEL, LF, CR, BS, TAB, ESC, FF.

	\377		Octal
	\xFF		Hex

	Can be used to match a character with specific ASCII code given in
octal or hex.

The escape sequences can be used inside of \[...] as well.
-- 
/*  jhallen@world.std.com (192.74.137.5) */               /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}

Joseph H Allen (jhallen@world.std.com) wrote:
> 	\377		Octal
> 	\xFF		Hex

> 	Can be used to match a character with specific ASCII code given in
> octal or hex.

    It would be nice if you could insert a character by it's
    ASCII code. I think it would be even more useful than
    functions "Next char is a control char" and "Next char has 7
    bit set".

    -=Kari=-
--
      Kari Likovuori - Helsingin yliopisto - Atk-keskus
            INTERNET: Kari.Likovuori@Helsinki.Fi              .~~.
      ** Akateemiset Hyv"an Oluen Yst"av"at (AHOY) **         |--|]
           ** Suomen Kotiolutyhdistys (SKOOL) **              |__|
   ** Suomen Itsen"aisten Olutseurojen Liitto (FINNLIBS) **

In article <Cv0B4q.EDu@world.std.com>,
Joseph H Allen <jhallen@world.std.com> wrote:
>In article <Cur3x5.A95@world.std.com>,
>Joseph H Allen <jhallen@world.std.com> wrote:
>>
>>                           Joe's Own Editor 1.0.12
>
>The latest version is now 1.0.13: please wait until that appears in the ftp
>directory before getting joe.
>
>Version 1.0.13 includes fixes for these bugs:

Also fixed in this release:

- A problem where a lot of OOPSs were printed when using the terminfo
  database on some systems.
-- 
/*  jhallen@world.std.com (192.74.137.5) */               /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}

In article <33f26u$fu5@kantti.Helsinki.FI>,
Kari Likovuori <likovuor@cc.Helsinki.FI> wrote:
>Joseph H Allen (jhallen@world.std.com) wrote:
>> 	\377		Octal
>> 	\xFF		Hex
>
>> 	Can be used to match a character with specific ASCII code given in
>> octal or hex.
>
>    It would be nice if you could insert a character by it's
>    ASCII code. I think it would be even more useful than
>    functions "Next char is a control char" and "Next char has 7
>    bit set".

That's a good idea- I just put it into version 1.0.13, which the sysop here
has still not coppied to the ftp directory (ftp.std.com, file:
src/editors/joe1.0.13.tar.Z).

You can type: `255  or  `xFF  or  `o377

to enter decimanl, hex or octal ASCII values directly.

-- 
/*  jhallen@world.std.com (192.74.137.5) */               /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}

In article <Cv1o5M.2GC@world.std.com>,
Joseph H Allen <jhallen@world.std.com> wrote:
> - A problem where a lot of OOPSs were printed when using the terminfo
>   database on some systems.

Term*INFO*?  Yeesh.  Termlib I believe, but I haven't heard of terminfo
doing that.
-- 
Peter da Silva                                            `-_-'
Network Management Technology Incorporated                 'U`
1601 Industrial Blvd.     Sugar Land, TX  77478  USA
+1 713 274 5180                       "Hast Du heute schon Deinen Wolf umarmt?"

In article <Cv1o5M.2GC@world.std.com>,
Joseph H Allen <jhallen@world.std.com> wrote:

>>>                           Joe's Own Editor 1.0.12
>>The latest version is now 1.0.13:

I got JOE working on an HP-9000/735.  It's the weirdest problem yet:
arithmetic involving shorts doesn't appear to work right.  Does anyone have
any idea why?  Here's a program to demonstrate the problem:

unsigned short a=1024;
unsigned short b=1024;
int c=311;
char *d="Hello there";

main()
 {
 printf("%x %x\n",d+c,d+a-(b-c));
 }

This printed: 40001207 400012d7

The fix for JOE is to change the two 'unsigned short's in the file b.h to
'int's.  This is truly a bizzare problem.

-- 
/*  jhallen@world.std.com (192.74.137.5) */               /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}

In article <Cv4GDy.GMr@world.std.com> jhallen@world.std.com (Joseph H Allen) writes:
>unsigned short a=1024;
>unsigned short b=1024;
>int c=311;
>char *d="Hello there";
>main() { printf("%x %x\n",d+c,d+a-(b-c)); }

>The fix for JOE is to change the two 'unsigned short's in the file b.h to
>'int's.  This is truly a bizzare problem.

The correct fix is to change the two '%x' conversions to '%hx' conversions.
%x requires an unsigned int argument; %hx requires an unsigned short argument.
--
 <<  If this were the company's opinion, I would not be allowed to post it.  >>
segmentation fault (california dumped)

diamond@jrd.dec.com (Norman Diamond) writes:

: In article <Cv4GDy.GMr@world.std.com> jhallen@world.std.com (Joseph H Allen) writes:
: >unsigned short a=1024;
: >unsigned short b=1024;
: >int c=311;
: >char *d="Hello there";
: >main() { printf("%x %x\n",d+c,d+a-(b-c)); }

: >The fix for JOE is to change the two 'unsigned short's in the file b.h to
: >'int's.  This is truly a bizzare problem.

: The correct fix is to change the two '%x' conversions to '%hx' conversions.
: %x requires an unsigned int argument; %hx requires an unsigned short argument.

In cases like this I'd say the correct fix is to finally dispose of 
that junk language "C".
Sorry - I could not resist once again. No replies necessary.
Thomas Wolff@inf.fu-berlin.de

In article <33kfu1$eff@usenet.pa.dec.com> diamond@jrd.dec.com (Norman Diamond) writes:
>In article <Cv4GDy.GMr@world.std.com> jhallen@world.std.com (Joseph H Allen) writes:
>>unsigned short a=1024;
>>unsigned short b=1024;
>>int c=311;
>>char *d="Hello there";
>>main() { printf("%x %x\n",d+c,d+a-(b-c)); }
>>
>>The fix for JOE is to change the two 'unsigned short's in the file b.h to
>>'int's.  This is truly a bizzare problem.

>The correct fix is to change the two '%x' conversions to '%hx' conversions.
>%x requires an unsigned int argument; %hx requires an unsigned short argument.

Sorry, I had noticed the "unsigned short" declarations and had not noticed
the "char *" declarations.  Someone pointed out by e-mail that these are
pointer expressions.  The correct fix is to use %p format (and pedantically,
to cast the pointer expressions to type (void *), but it is "intended" to
work without it because char * and void * have the same representation).
However, %hx or %x or %lx might work on some machines if you know the
sizes of the corresponding integral types and of char *.

[Notice to jik:  Sorry the amount of source here is only a few characters,
changing x or hx to p.  It is still source.]
--
 <<  If this were the company's opinion, I would not be allowed to post it.  >>
segmentation fault (california dumped)