Less Prompting? Duplicate Region Prompts me, Delete Region Prompts me...

Question

I understand that some people need to be reminded that they are doing something before they do it, but if I want to delete the region, why can't I hit delete and it vanishes? Instead I get prompted as to if I want to keep it or delete it. Can I set a default so this doesn't keep popping up? When arranging, I know what I want to delete, as I selected it, I will clean the bin when I'm finished with the session.
Here is the example, I just got finished typing a 25 page paper in MS Word, I want to delete sentences and words that I have written to clean it up, make it flow nicer, does MS Word say "Keep or Delete" on every word or paragraph I try to delete? No. In fact, it has never done that. Neither does nuendo, cubase, sonar, protools, ableton live, reason, energy xt, ardour - so what gives? Its an extra uneeded enter/return key press - and this millesecond counts in a session a client is paying for.
When I want to duplicate a region using command R - there's the prompt again - i know that it allows for you to specify how many times, but let me set a default. Yes I know I can control click drag to duplicate without the prompt, but lets say you want to duplicate by looking at the rest of your arrangement - should I have to count out how many times this region should occur, or keep control click dragging - or should I just be able to hit command D to my hearts content without prompting until everything lines up for me?
Again, small things that add up, my frustration comes from recording a vocalist last night with stacks galore, 45plus vocal tracks (the harmony spread ups the track count) duplicating and deleting - was more of a chore and an exercise in mouse movement than usable workflow.

Answer 1

Regina:
The buffer in sqlplus is intended to hold the last SQL statement or PL/SQL block issued. It is not really the same as a script, which can be an arbitrarily long sequence of sqlplus commands (like ACCEPT), SQL statements and/or PL/SQL blocks mixed any way that makes sense. Also, a named script is permanent, while the buffer gets overwritten each time.
You can kind of fool sqlplus into running several commands from the buffer, but only by running it as a script. But, only the last statement executed remains in the buffer at the end.
I edited the sql buffer (using ed at the sql prompt) to look like:
ACCEPT v NUMBER PROMPT 'Enter a number: ';
select &v from dual;Then saved the changes and ran the buffer file (afiedt.buf on my UNIX system) as a script and got.
ACCEPT v NUMBER PROMPT 'Enter a number: ';
select &v from dual;
SQL> @afiedt.buf
Enter a number: 5
old   1: select &v from dual
new   1: select          5 from dual
         5
         5Pretty much what you would expect. But, when I edited the buffer again I got
SQL>ed
select &v from dual
/So, I lost the ACCEPT command.
The other advantage to using scripts is that users do not need to type the whole set of SQL statments, just
@script_name (for the lazy) or
start script_name (for the more energetic).
HTH
John