Warning before major deletion

I know we get far too many “are you sure?” warning nowadays for something as mundane as allowing an app we said to run, but I’m a little concerned that I’ll fat-finger someday and accidentally delete a directory in one of my projects. When a directory in the binder is highlighted, one need only hit the delete key for it to be gone forever (at least, I think it’s forever).

This scares me a little, since I - like most people - don’t backup the way that I should. Perhaps a warning before deleting any directory in which there’s documents that contain anything would be appropriate here.

Thanks.

Everything that gets deleted goes into the ‘Trash’ folder. You can just drag it back out of there to recover the work.

To delete something completely, you need to choose to empty trash as well, which is not likely to happen accidentally.

Aha! I didn’t know that, and that will be very helpful if ever I make the mistake of accidental deletion. Good to know. Thanks!

This just goes to show that no one reads the help files. I don’t know why I’m surprised, given that I never read help files. I must have assumed that everyone else was better than me in this regard. :slight_smile: To whit:

From the Scrivener tutorial, under “Step 1: Beginnings”:

From the Help file, under “The Main Interface” section of “Getting Started”:

From the FAQ that appears both in the Tips & Tricks & FAQ section of this forum and in the Help file:

And yet this is still probably the most common complaint/question I get… The solution? The next update requires you to hit cmd-delete rather than just delete to move a file to the trash. (And if after the update comes out anyone e-mails me to say that hitting delete should move files to the Trash, I will murder them. :slight_smile: )

All the best,
Keith

Capn Keef!! Dont be mean, let Druid kill some ov `em!!

rat

I predict the shortcut in Scrivener 2.5 will be Cmd-Opt-Ctrl-Shift-Fn-Delete.

I think I am the only person that reads help files. Has anyone read the PDF for EagleFiler? Beautifully written, and in LaTeX, too. :slight_smile: Now the BBEdit manual, never made it all the way through that one; 'twas a monster!

I think help files would be better if they had more action scenes.

You know, our masked hero, the developer, slashing the throats of our villains, the users.

I never read help files either. Most of the time, if an application is worth using, most of it will come intuitively. I use them as a reference, to lookup how to do something if I am struggling, but I very rarely read them.

That being said, I have read Scrivener’s in its entirety, because I knew there was a lot of stuff it could do that I hadn’t even thought about. Never even downloaded EagleFiler, let alone read its help file. Maybe I should though, before I properly write my own…

As you yourself said, a good app really doesn’t require a manual for most functions. And seeing that the only person that seems to read manuals are the authors, AmberV, and Antony, wouldn’t it be better to work on more features?

All snarkyness aside, I agree with your premise that a decent user app should be intuitive. Maybe that should be a philosophical basis for a manual:

You probably want to word it differently if you adopt that line of reason. And you would need to make allowances for those with green matter and no gray matter. Otherwise vic-k will be lost.

Oh, just to clarify: I wasn’t trying to be mean to original poster at all! I was just saying that a lot of people have complained about this even though it’s mentioned in all those places, and that it probably would have got me too, had I not programmed it, given that I never would have bothered looking in those places either. :slight_smile: Hence the change…
All the best,
Keith

No, you’ll get hundreds of mails from existing users. “Keith, delete doesn’t work anymore! I press backspace as hard as I can! Fix it! Quick!”

Feel free to murder those, too. :wink:

Capn Keef, im confyoosed now! will druid get two kill em as asks daft cwestyens or not :confused:
rat

I did warn you :wink:

To no-one’s surprise, I read documentation too. Oh, for a life.

Fine. Be that way. Make me and vic-k look like the delinquent ones. It just goes to show you… Wait, I think we are the delinquent ones. Ummm … never mind.

But I ain’t editing that post for any more manual readers. You people are just weird.

I would like to take this opportunity to point out that: unlike the half-brain, but just like antony, I too read the documentation. However, unlike antony, I don`t understand it!! [size=150]I need documentation,[/size] that explains the documentation, [size=85]that explains the documentation[/size] [size=50]that explains the documentation[/size] [size=50]that explains…[/size].
vic

Delinquent still applies.

HOW TO GET PEOPLE TO READ THE HELP FILES

In the help files in random places give directions on how to find the “Easter Eggs” that are buried in Scrivener.

People love finding those easter eggs.

:slight_smile:

Guano Brain,
You wouldn`t be so foolish as to unleash Eliza…would you. I may not feel inclined to pull you all back from the brink this time.
Fluff

Hi–I’m a new user, and just searched for information on what seems to me the excessive easiness of accidentally moving files to the trash (by accidentally hitting Delete while a file is highlighted), and found this thread. I was very happy at the promised solution (requiring Command-delete instead), but I noticed that this was written in 2006. Might this still become a feature of Scrivener?

Hello!

Welcome to scriv.

Couple of points to emphasize:

  1. The trash folder is NOT emptied easily. So while the delete key CAN delete an item you can get it back until you empty the trash in scriv.
  2. Keith the Almighty is actively working on the next release. This feature is scheduled for that release. We hope to see it some time early next year.
  3. Vic-k is nuts.
  4. Wock is too.
  5. I may be, but I can’t tell.
  6. It is easier to post on this forum than to simply buckle down and do what I am really at my system to do.

See what you have done?