Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: Ubuntu Date: Wed, 19 Oct 2011 19:39:17 +0000 (UTC) Organization: UK Free Software Network Lines: 62 Message-ID: References: <9g5n98F5upU1@mid.individual.net> <9g5s6sFh1jU1@mid.individual.net> <9g81i2Fj6eU4@mid.individual.net> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1319053157 30950 84.45.235.129 (19 Oct 2011 19:39:17 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Wed, 19 Oct 2011 19:39:17 +0000 (UTC) User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:9008 On Wed, 19 Oct 2011 13:27:30 +0000, blmblm@myrealbox.com wrote: > In article , > Martin Gregorie wrote: >> On Tue, 18 Oct 2011 17:43:56 +0000, blmblm@myrealbox.com wrote: >> >> > There is that (the performance issue). My experience has been that >> > over a fast local network, it's good enough for most applications, >> > though I seem to remember that there are exceptions (though not what >> > they are). Over a not-so-fast network, yeah, it can be too slow to be >> > usable. >> > >> Same here - which is what I was speaking about. >> >> > Strongly agreed about the value of "screen" -- I've even been known >> > to use it locally, for its cut-and-paste features. >> > >> I've never gotten around to using screen, though I do normally use the >> microEmaxs editor everywhere - its multi-screen abilities combined with >> shelling out over the top of it do almost everything I need. > > For me the other benefit of "screen" is the one previously mentioned by > the person who first mentioned this tool -- it sets up something that > persists even if the network connection is broken, deliberately or not. > For me examples of both kinds of breakage do arise -- it's useful to be > able to set something up under "screen" at work, detach the screen > session, and reattach it later from home, or vice version, > and it's also useful to be able to set up something that will persist > even if the ssh session under which it was started times out. > >> Everything else is easily met with a few more ssh sessions in Gnome >> terminal windows, since its not a lot harder to cut 'n paste between >> those than it is within a multi-windowed terminal application. >> >> > Nice to know that there are at least a few other shell fans out >> > there? >> > >> Most of my programming activity is command-line oriented regardless of >> whether I'm driving a local or remote system, which I do with ssh and >> X11 forwarding: use of the latter boils down to developing Swing >> programs with much lower use of it to run remote copies of GIMP, >> LibreOffice progs, >> and firing up Opera remotely if I want to proof read Javadocs. > > Once upon a time you could proofread javadocs with a frames-capable > text-mode browser (such as elinks). Not so much with Java 7, > alas .... Maybe a rant for another thread, but at least a return from > topic drift? > Have you any idea why? I prefer just tried lynx, which I prefer to elinks, on a Java 6 javadocs set. It did a reasonable job despite insisting on the non-frames set of pages. Apart from that, the worst you can say about it is that its formatting of method parameters with long fully qualified types is somewhat untidy. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |