Feature request: Buffer for compile/shell command output flags

[V01D <phreakuencies@xxxxxxxxx>]

Hi,
I've noticed that when running a shell command or when using the compile 
option on the menu, and later closing the generated buffer (with the 
output from the corresponding command(s)), jed asks if I want to 
save/abort/kill the buffer.
Wouldn't it be nicer if the buffer created could be closed without any 
further confirmation?

I made the following modification to shell.sl:

--- shell.sl    2006-04-13 22:07:02.000000000 -0300
+++ shell.sl_   2006-04-13 21:59:33.000000000 -0300
@@ -102,10 +102,6 @@
    push_spot ();
    status = run_shell_cmd (cmd);
    pop_spot ();
-
-   variable dir, file, name, flags;
-   (file,dir,name,flags) = getbuf_info ();
-   setbuf_info (file,dir,name,(flags | (1 shl 3)) & ~(1 shl 0));

    vmessage ("Exit Status: %d", status);
 }

This makes the output buffer read-only and turns the "modified" bit off, 
after the output is inserted on it. This way, I can close the buffer 
without any confirmation.
The read-only part is not necessary but I feel that it is not desirable 
to use the output of the command as a standard editable buffer, but as a 
window holding the output.

I wouldn't request this as a feature if I had a way to change this by 
running something on my own *.sl files (in my home, loaded at startup).

Thanks,
Matt.

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.