Re: Unconditional prompting from dotfile packages

1999-05-03 Thread Josip Rodin
On Sun, May 02, 1999 at 01:56:06AM +0200, Martin Schulze wrote: > > What do you actually mean by unconditionally prompting - the message > > for bytecompilation? What do you propose, to automatically bytecompile? > > If I want to auto-compile one module it is likely that I want to > autocompile th

Re: Unconditional prompting from dotfile packages

1999-05-01 Thread Martin Schulze
Josip Rodin wrote: > On Wed, Apr 21, 1999 at 07:15:28PM -0700, Ben Gertzfield wrote: > > Drake>I'd like to see anything that prompts unconditionally > > Drake> dropped below Standard prioirity though. dotfile* come to > > Drake> mind. > > > > You're right, this is a complete pain

Re: Unconditional prompting from dotfile packages

1999-04-22 Thread Josip Rodin
On Thu, Apr 22, 1999 at 07:18:48PM +1000, Craig Sanders wrote: > > What do you actually mean by unconditionally prompting - the > > message for bytecompilation? What do you propose, to automatically > > bytecompile? > > is there any good reason not to do that? The only argument I see against aut

Re: Unconditional prompting from dotfile packages

1999-04-22 Thread Craig Sanders
On Thu, Apr 22, 1999 at 11:11:27AM +0200, Josip Rodin wrote: > What do you actually mean by unconditionally prompting - the > message for bytecompilation? What do you propose, to automatically > bytecompile? is there any good reason not to do that? or at least queue the job for execution when dpk

Re: Unconditional prompting from dotfile packages

1999-04-22 Thread Josip Rodin
On Wed, Apr 21, 1999 at 07:15:28PM -0700, Ben Gertzfield wrote: > Drake>I'd like to see anything that prompts unconditionally > Drake> dropped below Standard prioirity though. dotfile* come to > Drake> mind. > > You're right, this is a complete pain in the ass. Are the dotfile > p