vile
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vile] Xvile sort of daemonizing itself


From: Gary Jennejohn
Subject: Re: [vile] Xvile sort of daemonizing itself
Date: Sat, 27 Mar 2010 18:47:03 +0100

On Sat, 27 Mar 2010 09:32:55 -0400 (EDT)
Thomas Dickey <address@hidden> wrote:

> On Sat, 27 Mar 2010, Michael Tiernan wrote:
> 
> >
> > ----- Original Message -----
> > From: "Thomas Dickey" <address@hidden>
> > To: "Gary Jennejohn" <address@hidden>
> > Cc: address@hidden
> > Sent: Saturday, March 27, 2010 8:38:10 AM GMT -05:00 US/Canada Eastern
> > Subject: Re: [vile] Xvile sort of daemonizing itself
> >
> > On Sat, 27 Mar 2010, Gary Jennejohn wrote:
> >
> >> On Fri, 26 Mar 2010 03:31:34 -0400
> >> Steven Lembark <address@hidden> wrote:
> >>
> >>> On Fri, 12 Mar 2010 19:53:04 +0100
> >>> Gary Jennejohn <address@hidden> wrote:
> >>>
> >>>> I do not like this behavior because it screws up using xvile as the
> >>>> external editor in my claws-mail setup.
> >>>
> >>> My Config / Ext Programs / Text editor is set to:
> >>>
> >>>     /opt/bin/xvile +fork %s
> >>>
> >
> >> Is there any consensus on which setting should be used
> >> in the app-defaults file?
> >
> > Would it be too ugly to make the default behavior stay as is to make it 
> > easier on you *BUT* put the "fork-or-no-fork" flag in the system-wide or 
> > user level vilerc file?
> >
> > This would give a user the ability to set the flag themselves in their 
> > local (and easier to grok) rc file.
> 
> Perhaps (I'm not sure of the impact - right now, the X resources are read
> and processed before .vilerc is read and processed).
> 

I personally would prefer the forking to be off by default.  After all,
that was the behavior for years and years and never raised any protests :)

--
Gary Jennejohn




reply via email to

[Prev in Thread] Current Thread [Next in Thread]