![]() ![]() Frequently use it to terminate legacy batch (BAT) and modern command (CMD) files.īefore ctrl-x, ctrl-c, ctrl-v it was even more wacky: shift-del, ctrl-ins, shift-ins.Yep, learnt those on Win1.0 A situation which is still there in the default command line environment in Windows 37 years later! Um, Ctrl+C works in the Windows 9x era “Dos prompt” and in the NT Console window… not sure why it doesn’t for you. Which lead to unfortunate compromises like ctrl-c not working in the command window in Windows, because ctrl-c is generally used for interrupting running command line processes. My memory of history is different, MS used Shift+Insert and other odd combinations for Windows 1.0, through to 3.0, and only adopted the Ctrl+X, C, V in Windows 3.1 as part of adopting IBM’s Common User Access design guide. And they chose to add the CMD key to do these things. In reply to a post by andynormancx:Or because they were first (or at least the first to bring cut/copy/paste to a consumer graphical user interface). Re: Microsoft makes Outlook for Mac free to use I still use the Wordstar ctrl-k, b | ctrl-k, k | ctrl-k c | ctrl-k v combinations when I'm editing text over on Linux (I never did get to grips with the nonsense that is vi, first thing I do on a new Linux install is to add the Joe text editor).Ĭuriously ctrl-x, ctrl-c, ctrl-v work in Microsoft apps on the Mac, alongside the standard CMD based ones. Not to mention every text editor on MSDOS having completely different key combinations for cut/copy/paste. A situation which is still there in the default command line environment in Windows 37 years later!īefore ctrl-x, ctrl-c, ctrl-v it was even more wacky: shift-del, ctrl-ins, shift-ins. When Microsoft came to do the same thing they didn't have the luxury of designing their own keyboard so they were stuck with the control key. You'll be glad you did.Or because they were first (or at least the first to bring cut/copy/paste to a consumer graphical user interface). ![]() So if you're going to be using SpamSieve, keep a collection of spam in a separate folder for training before you begin. ![]() The instructions suggest fishing these out of your trash, but the problem is that if your spam is in the trash it's almost certainly mixed in with a lot of good messages and now you have to manually tease them apart. ![]() DON'T DO THIS! The training process requires about 600 representative spam messages. The instructions say to delete the messages in your current spam folder before setting up SpamSieve. I do have one complaint: the instructions for the initial training process are a little unclear, and in one place downright misleading. My spam problem is (I almost dare not say this for fear of tempting fate) effectively solved. I've had one false positive during the training process, and the false negatives have rapidly dwindled to 1-2 a day. I've only been using (which is to say training) it for three days, but the situation is already dramatically better than it was before. I was a little skeptical that it would work much better than Apple's built-in filter, but there's a 30-day free trial so I didn't have much to lose. I was about to throw up my hands in despair and set up a second mail server for Microsoft users, when I decided instead to try SpamSieve. One man's spam is another man's hot deal of the week from his favorite on-line vendor, and the training process can get really annoying if it's not integrated into the client. I could have installed a content-based spam filter on the server, but the problem is that spam is personal. I have clients using this server who use outlook, so I had to disable the FQDN requirement. As far as I have been able to determine, it is not possible to configure Microsoft Outlook on Windows to send an FQDN. Unfortunately, it works a little too well. This will prevent many botnet machines from connecting because they tend to not be configured to send a FQDN. One of the ways an SMTP server can cut down on spam is to require clients to connect with a fully qualified domain name (FQDN). I've recently started running my own mail server, so I started tweaking the settings to try to cut down on the processed breakfast meat, and discovered that Microsoft Outlook has a serious bug (what a surprise). I get a ton of spam, and it was starting to overwhelm the filter built in to the OS X mail client. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |