[GRASS-dev] return of the OSX xterm question

[Glynn Clements]

William Kyngesburye wrote:

> >> But mainly, I can't understand how the xterm compatibility part would
> >> work: to be able to handle the xterm flags, it has to be able to run
> >> from the CLI, but when run from the CLI an application executable
> >> opens a completely new instance of the whole application, not a new
> >> window (exactly the same problem as the browser issue I'm working  
> >> on).
> >
> > And what's the problem with that?
> >
> > I can see why this might be a problem for a browser; I don't see why
> > it's a problem for a terminal.
> 
> It's a general OSX problem/quirk when running any .app application  
> from the CLI.  If the application is already running, you don't get a  
> new window in the application (or whatever the default action is,  
> depending on what is passed to it).  New instances of whole  
> applications is not the way to run OSX apps.
> 
> Instead, you must tell the system to open a file with a particular  
> application (the 'open' CLI command) so the system can take care of  
> deciding whether the application is already running.

That doesn't address my point.

What is the problem with having each terminal window belong to a
separate process? Or, from a different perspective, what is the
advantage to having a single process manage multiple terminal windows?

I can see some advantages for a browser, but not for a terminal.

-- 
Glynn Clements <glynn at gclements.plus.com>