assigning keys
in [SAS]
|
From: xlr82sas on 2 Mar 2010 13:20 On Mar 2, 7:23 am, nathaniel.wood...(a)DOM.COM (Nathaniel Wooding) wrote: > Masoud > > Rather than using a pf key combination, would a icon on the tool bar be useful? > > Click > > Tools > Customize Tools > Select the Customize tab > Click on the Add Tool icon (it is on the left of the row of tools above the command line entry window > In the command window, enter your SAS statements > In the Help Text and Tip Text, enter some explanatory text > Click on the Chang Icon icon and select an icon > Click on OK > > I have such a button set up to clear my log and output windows and then submit the code in the display manager. The command line reads > > lst;clear;log;clear;wpgm;submit > > The alternative for defining an actual pf key is , in the display manager window's command bar, type KEYS and hit enter. Type in whatever SAS commands you wish next to your particular pf key combination and close the window.. > > Nat Wooding > > > > -----Original Message----- > From: SAS(r) Discussion [mailto:SA...(a)LISTSERV.UGA.EDU] On Behalf Of Masoud Pajoh > Sent: Tuesday, March 02, 2010 9:47 AM > To: SA...(a)LISTSERV.UGA.EDU > Subject: assigning keys > > I want to run: > proc fsedit data=Temp.ProgDescriptions screen=sasuser.screens. > ProgDescriptions; run; > > by assigning it to a key, e.g. alt+f1. > How can I do that? > > Thanks, > > Masoud > CONFIDENTIALITY NOTICE: This electronic message contains > information which may be legally confidential and or privileged and > does not in any case represent a firm ENERGY COMMODITY bid or offer > relating thereto which binds the sender without an additional > express written confirmation to that effect. The information is > intended solely for the individual or entity named above and access > by anyone else is unauthorized. If you are not the intended > recipient, any disclosure, copying, distribution, or use of the > contents of this information is prohibited and may be unlawful. If > you have received this electronic transmission in error, please > reply immediately to the sender that you have received the message > in error, and delete it. Thank you.- Hide quoted text - > > - Show quoted text - I don't use the command bar, I use command lines on each window but if you type fse sashelp.class it will open fsedit Art has an excellent paper on setting up very general easy to use functions for this type of action and many others. You can find information about fse, fsv and fsb and others on my site: http://homepage.mac.com/magdelina/.Public/utl.html utl_tipweb.txt /* T002790 SAS DISPLAY MANAGER COMMANDS AND SCRIPTS OLD EDITOR */ /* T002580 SAS KEYBOARD ABREVIATIONS BY WAY OF COMMAND MACROS */ NOTE NONE OF THIS WILL WORK WITH THE SUPER ENHANCED ENTERPRISE GUIDE EDITOR (EG) SOAPBOX ON MOST PROGRAMMERS UNDERESTIMATE THE POWER OF THE COMMAND LINE AND COMMAND SCRIPTS GUIs LIKE EG HAVE THERE PLACE BUT SHOULD NOT FORGO THE COMMAND LINE SOAPBOX OFF for example fse fsv fsb libn filen fslist vt I have wtritten at leat 50 others over the years. /* T002790 SAS DISPLAY MANAGER COMMANDS AND SCRIPTS OLD EDITOR */ The prefix area Many of these commands can be put on function keys using a ':', ie :ts. D99---- Delete next 99 lines (also could cut with mouse) I999--- Insert 999 blank lines useful when autoadd is set IB55--- Insert 55 lines before C3----- Copy next three lines to some target A000102 Target for line copy or include file (copy after) B000102 Target for line copy or include file (copy before) M------ Move this line somewhere M3----- Move next 3 lines somewhere O3----- Move source lines over these lines R3----- Replicate the next 3 lines DD00103 Block delete CC00103 Block Copy MM00103 Block Move 0000104 0000104 0000104 DD----- CC----- MM----- OO00103 Target Over RR3---- Block Replicate 0000104 0000104 OO----- RR----- (4----- Shift left first 4 columns into bit bucket (distructive shift) )4----- Shift right first 4 columns (distructive shift) >5----- Nondistructive shift right <5----- Nondistructive shift left >>5---- Non distructive shift right of a block of commands 0000101 0000102 >>----- <<,)),(( Similar to single character versions UC----- Upper case line - more useful on function key as :UC UC26--- Upper case next 26 lines LC----- Lower case line LC26 LLC---- Block of lines -lower caSE UUC TF----- Text flow lines until blank line TS----- Text split at cursor better on function key as :tf MASK - BUILD TEMPLATE FOR ENTERING DATA no need to look up a P- Value put this on any command line %put %sysfunc(probnorm(1.96)); /* try this on command line */ ? - previous command history subtop - submit top line of editor rchange - change on function key hit rfind - find on function key hit save prg /# save program in your profile #/ copy prg /# recalls program from your profile #/ change - c today yesterday ic all ( ignore case all) cols reset keys top bot n - scroll down to line n left n right n spell all - check spelling of all words in editor autoadd - add aline at a time to editor ( usewith mask and bounds ) vscroll 25 - set scroll amounts for forward and backward hscroll 10 backward max n forward max n bounds mask copy paste find - f 'data' first last next prev prefix suffix word find 'Mac' prefix change - c todat yesterday ic all rchange - change on function key hit rfind - find on function key hit mark - highlight string, lines for submit or edit mark block - highlight rectangle within editor does not have to be full lines store zoom z up 2 down 4 CAPS on/ off home cursor nums on/ off %let vt pmenu off /# functon key #/ pmenu on end submit unmark unmark all tabs redo nums on/off fse fsv fsb libn filen fslist vt Example 1 -- Just a dumb script -------------------------------- 1;F ' ';MARK;HOME; 2;HOME;MARK;HOME;STORE;HOME;UNMARK; If the first line in active editor contains 000001 %Macro MyLongMacroName This script will put MyLongMacroName into the paste buffer. You can then paste MyLongMacroName anywhere you want. (This only works on windows). Try it, just copy the one line script to the command line.
From: Nathaniel Wooding on 2 Mar 2010 13:13 Masoud I got curious about how to get a tool to execute a Proc so I did some readi= ng. In the MS companion, they offer examples that were helpful. It appears = that you need to store your code in a program file and then include it. Hen= ce, I stored Proc Fsedit data =3D ... etc; run; In a file that I called Keytest.SAS. Then, I changed my tool command to rea= d WhostEDIT;include c:\park\keytest.sas;submit WHOSTEDIT opens a new editor window. Note that the include does NOT have a= % sign and the path does not have quotes. The submit kicks off the job. If you wanted to be able to supply a sas data set name, you could have a %w= indow statement in your job and use that to enter the set name and pass it = to the FSEDIT. Nat From: mpajoh(a)ODOT.ORG [mailto:mpajoh(a)ODOT.ORG] Sent: Tuesday, March 02, 2010 11:24 AM To: Nathaniel Wooding (Services - 6) Cc: 'SAS-L(a)LISTSERV.UGA.EDU' Subject: RE: assigning keys I tried the first method, but after I typed: proc fsedit data=3DTemp.ProgDescriptions screen=3Dsasuser.screens.ProgDescr= iptions; run; in the command box clicked ok, and confirmed that I want to save changes to= the SASEDIT_MAIN profile, I get: ERROR: General error from the User Interface subsystem. I had tried the second method before, and that does not do anything!! Thanks for the suggestions, Masoud Nathaniel Wooding <nathaniel.wooding(a)dom.com> 03/02/2010 09:25 AM To "'mpajoh(a)ODOT.ORG'" <mpajoh(a)odot.org>, "'SAS-L(a)LISTSERV.UGA.EDU'" <SAS-L(a)LI= STSERV.UGA.EDU> cc Subject RE: assigning keys Masoud Rather than using a pf key combination, would a icon on the tool bar be use= ful? Click Tools Customize Tools Select the Customize tab Click on the Add Tool icon (it is on the left of the row of tools above the= command line entry window In the command window, enter your SAS statements In the Help Text and Tip Text, enter some explanatory text Click on the Chang Icon icon and select an icon Click on OK I have such a button set up to clear my log and output windows and then sub= mit the code in the display manager. The command line reads lst;clear;log;clear;wpgm;submit The alternative for defining an actual pf key is , in the display manager w= indow's command bar, type KEYS and hit enter. Type in whatever SAS commands= you wish next to your particular pf key combination and close the window. Nat Wooding -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On Behalf Of Masoud= Pajoh Sent: Tuesday, March 02, 2010 9:47 AM To: SAS-L(a)LISTSERV.UGA.EDU Subject: assigning keys I want to run: proc fsedit data=3DTemp.ProgDescriptions screen=3Dsasuser.screens. ProgDescriptions; run; by assigning it to a key, e.g. alt+f1. How can I do that? Thanks, Masoud CONFIDENTIALITY NOTICE: This electronic message contains information which may be legally confidential and or privileged and does not in any case represent a firm ENERGY COMMODITY bid or offer relating thereto which binds the sender without an additional express written confirmation to that effect. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
From: Masoud Pajoh on 2 Mar 2010 13:35 This works great. Thanks, Masoud Nathaniel Wooding <nathaniel.wooding(a)DOM.COM> Sent by: "SAS(r) Discussion" <SAS-L(a)LISTSERV.UGA.EDU> 03/02/2010 12:20 PM Please respond to Nathaniel Wooding <nathaniel.wooding(a)DOM.COM> To SAS-L(a)LISTSERV.UGA.EDU cc Subject Re: assigning keys Masoud I got curious about how to get a tool to execute a Proc so I did some reading. In the MS companion, they offer examples that were helpful. It appears that you need to store your code in a program file and then include it. Hence, I stored Proc Fsedit data = ... etc; run; In a file that I called Keytest.SAS. Then, I changed my tool command to read WhostEDIT;include c:\park\keytest.sas;submit WHOSTEDIT opens a new editor window. Note that the include does NOT have a % sign and the path does not have quotes. The submit kicks off the job. If you wanted to be able to supply a sas data set name, you could have a %window statement in your job and use that to enter the set name and pass it to the FSEDIT. Nat From: mpajoh(a)ODOT.ORG [mailto:mpajoh(a)ODOT.ORG] Sent: Tuesday, March 02, 2010 11:24 AM To: Nathaniel Wooding (Services - 6) Cc: 'SAS-L(a)LISTSERV.UGA.EDU' Subject: RE: assigning keys I tried the first method, but after I typed: proc fsedit data=Temp.ProgDescriptions screen=sasuser.screens.ProgDescriptions; run; in the command box clicked ok, and confirmed that I want to save changes to the SASEDIT_MAIN profile, I get: ERROR: General error from the User Interface subsystem. I had tried the second method before, and that does not do anything!! Thanks for the suggestions, Masoud Nathaniel Wooding <nathaniel.wooding(a)dom.com> 03/02/2010 09:25 AM To "'mpajoh(a)ODOT.ORG'" <mpajoh(a)odot.org>, "'SAS-L(a)LISTSERV.UGA.EDU'" <SAS-L(a)LISTSERV.UGA.EDU> cc Subject RE: assigning keys Masoud Rather than using a pf key combination, would a icon on the tool bar be useful? Click Tools Customize Tools Select the Customize tab Click on the Add Tool icon (it is on the left of the row of tools above the command line entry window In the command window, enter your SAS statements In the Help Text and Tip Text, enter some explanatory text Click on the Chang Icon icon and select an icon Click on OK I have such a button set up to clear my log and output windows and then submit the code in the display manager. The command line reads lst;clear;log;clear;wpgm;submit The alternative for defining an actual pf key is , in the display manager window's command bar, type KEYS and hit enter. Type in whatever SAS commands you wish next to your particular pf key combination and close the window. Nat Wooding -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On Behalf Of Masoud Pajoh Sent: Tuesday, March 02, 2010 9:47 AM To: SAS-L(a)LISTSERV.UGA.EDU Subject: assigning keys I want to run: proc fsedit data=Temp.ProgDescriptions screen=sasuser.screens. ProgDescriptions; run; by assigning it to a key, e.g. alt+f1. How can I do that? Thanks, Masoud CONFIDENTIALITY NOTICE: This electronic message contains information which may be legally confidential and or privileged and does not in any case represent a firm ENERGY COMMODITY bid or offer relating thereto which binds the sender without an additional express written confirmation to that effect. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
From: xlr82sas on 2 Mar 2010 14:12 On Mar 2, 10:35 am, mpa...(a)ODOT.ORG (Masoud Pajoh) wrote: > This works great. > > Thanks, > > Masoud > > Nathaniel Wooding <nathaniel.wood...(a)DOM.COM> > Sent by: "SAS(r) Discussion" <SA...(a)LISTSERV.UGA.EDU> > 03/02/2010 12:20 PM > Please respond to > Nathaniel Wooding <nathaniel.wood...(a)DOM.COM> > > To > SA...(a)LISTSERV.UGA.EDU > cc > > Subject > Re: assigning keys > > Masoud > > I got curious about how to get a tool to execute a Proc so I did some > reading. In the MS companion, they offer examples that were helpful. It > appears that you need to store your code in a program file and then > include it. Hence, I stored > > Proc Fsedit data = ... etc; run; > In a file that I called Keytest.SAS. Then, I changed my tool command to > read > > WhostEDIT;include c:\park\keytest.sas;submit > > WHOSTEDIT opens a new editor window. Note that the include does NOT have > a % sign and the path does not have quotes. The submit kicks off the job. > > If you wanted to be able to supply a sas data set name, you could have a > %window statement in your job and use that to enter the set name and pass > it to the FSEDIT. > > Nat > > From: mpa...(a)ODOT.ORG [mailto:mpa...(a)ODOT.ORG] > Sent: Tuesday, March 02, 2010 11:24 AM > To: Nathaniel Wooding (Services - 6) > Cc: 'SA...(a)LISTSERV.UGA.EDU' > Subject: RE: assigning keys > > I tried the first method, but after I typed: > proc fsedit data=Temp.ProgDescriptions > screen=sasuser.screens.ProgDescriptions; run; > in the command box clicked ok, and confirmed that I want to save changes > to the SASEDIT_MAIN profile, I get: > ERROR: General error from the User Interface subsystem. > > I had tried the second method before, and that does not do anything!! > > Thanks for the suggestions, > > Masoud > > Nathaniel Wooding <nathaniel.wood...(a)dom.com> > > 03/02/2010 09:25 AM > > To > > "'mpa...(a)ODOT.ORG'" <mpa...(a)odot.org>, "'SA...(a)LISTSERV.UGA.EDU'" > <SA...(a)LISTSERV.UGA.EDU> > > cc > > Subject > > RE: assigning keys > > Masoud > > Rather than using a pf key combination, would a icon on the tool bar be > useful? > > Click > > Tools > Customize Tools > Select the Customize tab > Click on the Add Tool icon (it is on the left of the row of tools above > the command line entry window > In the command window, enter your SAS statements > In the Help Text and Tip Text, enter some explanatory text > Click on the Chang Icon icon and select an icon > Click on OK > > I have such a button set up to clear my log and output windows and then > submit the code in the display manager. The command line reads > > lst;clear;log;clear;wpgm;submit > > The alternative for defining an actual pf key is , in the display manager > window's command bar, type KEYS and hit enter. Type in whatever SAS > commands you wish next to your particular pf key combination and close the > window. > > Nat Wooding > > > > -----Original Message----- > From: SAS(r) Discussion [mailto:SA...(a)LISTSERV.UGA.EDU] On Behalf Of > > Masoud Pajoh > Sent: Tuesday, March 02, 2010 9:47 AM > To: SA...(a)LISTSERV.UGA.EDU > Subject: assigning keys > > I want to run: > proc fsedit data=Temp.ProgDescriptions screen=sasuser.screens. > ProgDescriptions; run; > > by assigning it to a key, e.g. alt+f1. > How can I do that? > > Thanks, > > Masoud > CONFIDENTIALITY NOTICE: This electronic message contains > information which may be legally confidential and or privileged and > does not in any case represent a firm ENERGY COMMODITY bid or offer > relating thereto which binds the sender without an additional > express written confirmation to that effect. The information is > intended solely for the individual or entity named above and access > by anyone else is unauthorized. If you are not the intended > recipient, any disclosure, copying, distribution, or use of the > contents of this information is prohibited and may be unlawful. If > you have received this electronic transmission in error, please > reply immediately to the sender that you have received the message > in error, and delete it. Thank you.- Hide quoted text - > > - Show quoted text - Hi All, I think this also works fse sashelp.class screen=sasuser.screens You can put this on a function key
From: templerr on 2 Mar 2010 23:11
Personally I use the KEYDEF command in my autoexec.sas - that way I get my customised key definitions no matter how many SAS sessions I am running. Note that I have only used this under Windows. dm 'KEYDEF "CTL R" "zoom off;Rsubmit"' ; Cheers Robin ----- Original Message Follows ----- > This works great. > > Thanks, > > Masoud > > > > > > Nathaniel Wooding <nathaniel.wooding(a)DOM.COM> > Sent by: "SAS(r) Discussion" <SAS-L(a)LISTSERV.UGA.EDU> > 03/02/2010 12:20 PM > Please respond to > Nathaniel Wooding <nathaniel.wooding(a)DOM.COM> > > > To > SAS-L(a)LISTSERV.UGA.EDU > cc > > Subject > Re: assigning keys > > > > > > > Masoud > > I got curious about how to get a tool to execute a Proc so > I did some reading. In the MS companion, they offer > examples that were helpful. It appears that you need to > store your code in a program file and then include it. > Hence, I stored > > Proc Fsedit data = ... etc; run; > In a file that I called Keytest.SAS. Then, I changed my > tool command to read > > WhostEDIT;include c:\park\keytest.sas;submit > > WHOSTEDIT opens a new editor window. Note that the > include does NOT have a % sign and the path does not have > quotes. The submit kicks off the job. > > If you wanted to be able to supply a sas data set name, > you could have a %window statement in your job and use > that to enter the set name and pass it to the FSEDIT. > > Nat > > From: mpajoh(a)ODOT.ORG [mailto:mpajoh(a)ODOT.ORG] > Sent: Tuesday, March 02, 2010 11:24 AM > To: Nathaniel Wooding (Services - 6) > Cc: 'SAS-L(a)LISTSERV.UGA.EDU' > Subject: RE: assigning keys > > > I tried the first method, but after I typed: > proc fsedit data=Temp.ProgDescriptions > screen=sasuser.screens.ProgDescriptions; run; > in the command box clicked ok, and confirmed that I want > to save changes to the SASEDIT_MAIN profile, I get: > ERROR: General error from the User Interface subsystem. > > I had tried the second method before, and that does not do > anything!! > > Thanks for the suggestions, > > Masoud > > > Nathaniel Wooding <nathaniel.wooding(a)dom.com> > > 03/02/2010 09:25 AM > > To > > "'mpajoh(a)ODOT.ORG'" <mpajoh(a)odot.org>, > "'SAS-L(a)LISTSERV.UGA.EDU'" <SAS-L(a)LISTSERV.UGA.EDU> > > cc > > Subject > > RE: assigning keys > > > > > > > > Masoud > > Rather than using a pf key combination, would a icon on > the tool bar be useful? > > Click > > Tools > Customize Tools > Select the Customize tab > Click on the Add Tool icon (it is on the left of the row > of tools above the command line entry window > In the command window, enter your SAS statements > In the Help Text and Tip Text, enter some explanatory text > Click on the Chang Icon icon and select an icon > Click on OK > > > I have such a button set up to clear my log and output > windows and then submit the code in the display manager. > The command line reads > > lst;clear;log;clear;wpgm;submit > > The alternative for defining an actual pf key is , in the > display manager window's command bar, type KEYS and hit > enter. Type in whatever SAS commands you wish next to your > particular pf key combination and close the window. > > Nat Wooding > > -----Original Message----- > From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On > Behalf Of Masoud Pajoh > Sent: Tuesday, March 02, 2010 9:47 AM > To: SAS-L(a)LISTSERV.UGA.EDU > Subject: assigning keys > > I want to run: > proc fsedit data=Temp.ProgDescriptions > screen=sasuser.screens. ProgDescriptions; run; > > by assigning it to a key, e.g. alt+f1. > How can I do that? > > Thanks, > > Masoud > CONFIDENTIALITY NOTICE: This electronic message contains > information which may be legally confidential and or > privileged and does not in any case represent a firm > ENERGY COMMODITY bid or offer relating thereto which binds > the sender without an additional express written > confirmation to that effect. The information is intended > solely for the individual or entity named above and access > by anyone else is unauthorized. If you are not the > intended recipient, any disclosure, copying, distribution, > or use of the contents of this information is prohibited > and may be unlawful. If you have received this electronic > transmission in error, please reply immediately to the > sender that you have received the message in error, and > delete it. Thank you. |