Re: Avoiding shell window popup on cygwin xemacs


"Vin Shelton" <acs@xxxxxxxxxx> wrote in message
news:m3bqx5s7mn.fsf@xxxxxxxxxxxxxxx

HASM wrote:
antonio.ramirez@xxxxxxxxx writes:

> Every time xemacs starts a process (e.g., gnuserv.exe, or a latex
> process), it pops up an annoying empty shell window. ... The canonical
> way to avoid it is to prefix the cygwin program by /bin/run.exe.
However,
> up until this latest update (to 21.4, patch 13), this hadn't been
> necessary under xemacs.

> I really like gnuserv to be running since I managed (after much pain)
for
> Windows explorer to use gnuclient as the default application for text
> files.

Try using winclient.exe instead of gnuclient (with run.exe)

antonio.ramirez@xxxxxxxxx writes:

That would not solve the problem. The problem occurs when xemacs itself
runs gnuserv, not when gnuclient is called to open a window in the
xemacs. (As I said, I've solved the issue of getting Windows to call
gnuclient. The problem now is getting xemacs not to pop up the annoying
CMD window when it runs external programs, like gnuserv... this didn't
use to happen before.)


Before Steve Youngs beats me to it :-) - please don't remove context when
replying to usenet posts. The only reason I had even the vaguest idea
of what you were talking about is that I read HASM's post immediately
before I read your response.

HTH,
Vin Shelton


There is no uniform Netetiquette about providing or deleting
context in Usenet posts. Each forum has its own established
custom. Some moderated forums will reject posts for quoting
"excess verbiage" or the moderator will delete "extra" quoted
material. Some forums are permissive about top-posting.

You will find that some posters who read a high volume of
posts and respond to them have their own agenda about what
makes it easy for them to do this and whether or not this should
be considered a "rule" rather than a figment of their imagination.

Another thing is the clash of custom developed on mailing lists
with a stream of uncategorized posts which evolved into reading
news organized and collected by Subject: where the expression
'following a thread' carried a stronger ethical imperative than a
prohibition on editing out excess quoting. A person is/was
expected to read the entire thread rather than jumping into the
middle of it and responding. Of course I've seen replies that
have snipped the previous post completely and have no context
at all, except the numbered identifiers of previous posts. So there
is a balance between context and requoting the entire post.

People that reply to a lot of email don't take the time to understand
what is written and often misinterpret it because they are in a hurry.
They also start their responses before reading the entire post. Often
they criticize some point made early in a post. So when the OP later
clarifies some issue made earlier in his post, it often turns out that
the OP's clarification makes the same point as the high-volume
pseudo-criticizing "expert". So when the OP reads the response
to his post he doesn't know if the criticism actually disagrees with
what he wrote, or there was agreement but the high-volume poster
was in too much of a hurry to go back and edit out his criticism
after reaching the point in the OP post which made the same point
that the high-volume poster thinks needs clarification. That is a lack
of courtesy that cannot be corrected by reading the thread in order
to gather the context if it seems insufficient. So while quoting all of the
original post might be considered providing context by the customs
of this particular group, comp.emacs.xemacs, it is not _Usenet_ policy
nor consensus custom, but the fulfillment of certain personal desires
which conserves their time at the expense of wasting other people's time.
In my experience those desires are often owned by high-volume posters,
who grandiosely appoint themselves as netcops for self-convenience.

If the shoe fits, only wear it then,
cyberdiction

WXPNews: Vol. 6, #8 - Feb 20, 2006 - Issue #215

EDITOR'S CORNER
Network Etiquette: Is It a Lost Cause?
[citing authority contrary to that represented as belonging to Steve Youngs]



.

Relevant Pages

  • Re: Why cant I see static variables in debug window
    ... Auto pane of the variable window, because you're about to use it (to add ... you can use the Locals pane to see everything... ... if you're *using* the static in the context where you ... Variables debug window, the value of the variable x does not show. ...
    (microsoft.public.windowsce.embedded)
  • RE: debugger IDE hangs when stepping with properties in watch wind
    ... Thanks - but as I'm typically changing context with each step (from one ... adding and then removing items from the watch ... window before each step isn't really very helpful - basically, ... > watch window, it will cost debugger much time to resolve these variables, ...
    (microsoft.public.vsnet.debugging)
  • Re: saveconf .user-file
    ... i want them to save the buffer information into a predefined directory ... Save context of all Emacs windows. ... saved is determined by the startup directory for XEmacs. ...
    (comp.emacs.xemacs)
  • Re: How can I get mouse shortcuts to work in Excel
    ... The Intermediate window is from the Visual Basic Editor. ... There is no right click menu (context menu missing). ... > Hi Dave, Thanks for the response. ...
    (microsoft.public.excel.setup)
  • Re: Avoiding shell window popup on cygwin xemacs
    ... it pops up an annoying empty shell window. ... > necessary under xemacs. ... Try using winclient.exe instead of gnuclient ... runs gnuserv, not when gnuclient is called to open a window in the ...
    (comp.emacs.xemacs)