Thanks, Thomas, for the detailed instructions for killing skim script. Jan: yes -- that is the ideal situation: saving on quit, but not prompting for save.
(I hate to invoke comparisons to Mac Preview, but it does do this by default. On Fri, Mar 22, 2019 at 10:18 AM Jan David Hauck <[email protected]> wrote: > It might be that Jacob is not referring to discarding changes upon save, > but instead to automatically keeping them without being prompted, as other > Mac Apps now do when the General System Pref "Ask to keep changes when > closing documents" is unselected. > > I was wondering this too recently. Is that possible? > (the general system pref doesn't seem to have an effect on Skim) > > > > > > > On Fri, Mar 22, 2019 at 5:34 AM Schneider, Thomas (NIH/NCI) [E] via > Skim-app-users <[email protected]> wrote: > >> jacob: >> >> > > Is it possible to quit without being prompted to save changes to >> > > open files? I highlight documents & leave many open simultaneously. >> > > Then I must click thru dozens of 'save changes' dialogue boxes before >> > > quitting. >> > >> > No. If you make changes to a document you are expected to want to >> > save them. Otherwise why would you want to make changes. If you forget >> > to save those changes woyld be losy, without you even knowing. That >> > would be a problem. >> >> While Christiaan is right - he would not want Skim to drop data - I >> can see that you might like to mark up something as you read and then >> throw it away. I do that on physical paper all the time! >> >> On a Unix system you could kill the Skim process. You might need kill >> -9 to force it to die. That's somewhat nasty and might leave things >> in a bad state but it might be effective. On MacOS you could make a >> script (write in Terminal using vim) and put a link to it on your >> desktop (ln -s) - then just double click the link and ALL skim >> processes would be killed. So the first part of the script would be >> to locate skim processes using for example: >> >> % ps -A | grep Skim | grep -v grep >> 87907 ?? 1:24.17 /Applications/Skim.app/Contents/MacOS/Skim >> >> Then capture the first word: >> >> % ps -A | grep Skim | grep -v grep | awk '{print $1}' >> 87907 >> >> % set skimprocess = `ps -A | grep Skim | grep -v grep | awk '{print $1}'` >> % echo $skimprocess >> 87907 >> >> Then kill the process: >> % kill -9 $skimprocess >> >> Bingo! My skim process went away! >> >> Here's the complete 'killskim' script: >> === >> #!/bin/tcsh -f >> #(ie run the tshell on this but don't read the .cshrc or .tcshrc) >> >> echo version = 1.00 of killskim 2019 Mar 22 >> # 2019 Mar 22, 1.00: origin >> >> echo "usage: killskim" >> echo "kill the Skim process" >> >> set skimprocess = `ps -A | grep Skim | grep -v grep | awk '{print $1}'` >> echo "Skim process id: $skimprocess" >> kill -9 $skimprocess >> === >> >> You will need to make it executable: >> % chmod a+rx killskim >> >> You could put that on your desktop. Double click to run it. >> >> Tom >> >> Thomas D. Schneider, Ph.D. >> Senior Investigator >> National Institutes of Health >> National Cancer Institute >> Center for Cancer Research >> RNA Biology Laboratory >> Biological Information Theory Group >> Frederick, Maryland 21702-1201 >> [email protected] >> https://alum.mit.edu/www/toms >> >> >> _______________________________________________ >> Skim-app-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/skim-app-users >> > _______________________________________________ > Skim-app-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/skim-app-users >
_______________________________________________ Skim-app-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/skim-app-users
