I got tired of my googlemail inbox filling up with facebook emails. After some research, here is how i stopped them. Remember that i am writing this in nov.2013, so this may not work if Facebook change their tools.
1. Sign in to FB
2. Click photo to see larger view
3. When you click EDIT this panel appears.
4. Change this setting to ‘Only…’. If you see a SAVE button you should clikc that to confirm that’s what you want to do, then click close.
5. The other place you may need to adjust is in the ‘App Requests and Activity’ section at the bottom of the screen. I clicked that to reveal all the tools and apps that are loaded into my F/B account. A few of these apps were ones that i’d chosen, but most were not. So when you click ‘Apps…’ you should see the below. Your list will vary. Uncheck the check box after the apps you do NOT want to send you junk mail. If you see a SAVE button, you should click that to make it permanent. Then click close.
6. Do some F/B action that would cause an email to be sent, or get your friends to do so. Check the email address that belongs to your primary email a/c. Hopefully this should correct the problem.
7. If that does not stop them all, you may need to EDIT other Notification settings from step 2. Just uncheck them and hopefully stop them from sending you stuff. Good luck 🙂
Ok, here is a screen snippet of what our test2.html page looks like when rendered by a browser. Notice each color fragment has it’s code keywords colored according to the language of the fragment. Also note that the ‘Midnight’ theme is used for all code fragment displays. Click to grow.
Here is my test folder with a ‘styles’ sub-folder for the test2.html file. The HTML for our example test page follows. As Alex explains in his installation page, there are two approaches to markup of code fragments :
Use the html <pre> tag
Use the html <script> tag witha CDATA extension
For overall color control, five CSS files declare 1) the core colors 2) a theme default if no override theme has been chosen and 3) in this case we do use an overriding theme called ‘Midnight’. There are several other themes you can try.
Points to note in the following html document – both styles of highlighting are used. The <pre> element needs a class declaration for the brush (programming language) contained within the fragment. You can see class=’brush: groovy’ in the first fragment to color groovy keywords. The <script type=”syntaxhighlighter” class=”brush: js”><![CDATA[ declaration is the alternative approach to present code fragments. We can place any < or > characters within the CDATA of a script declaration otherwise if we use the pre approach, we need to manually change each < and > for their < and > equivalents.
Finally, look at the bottom of the html to see how we invoke syntax highlighter. We can invoke it only after the page has loaded completely. Here is a nice use of JQuery as it has a convenient function of $(document).ready(); which is called upon page load completion. It’s a nice place to insert our call to fire up the highlighter engine. Copy the code above into a textfile named test2.html and then use your favorite browser to open this file. If you’ve done it all correctly, you’ll be rewarded with a display like the screen snippet shown at the top of this post.
It look quite a while to figure out all these bits and pieces. The website documentation is sparse hence a steep lerning curve. Hope this helps you a bit. 🙂
Writing a blog can be fun and possibly, for the reader, educational. As i enjoy technology, it satisfies a creative urge to write on discoveries i come across in the wonderful world of technology. Often this takes the form of developing code for various platforms in a variety of different languages. One problem i find in blogging platforms is the ability to format and display segments of software code in a pleasing fashion.This wordpress platform has several features to do so.
The html <pre> and <code> elements provide some scope for this. With these html tags, i can present fragments of code and script in several languages. The actual presentation of these elements can be marked up with additional CSS. This gives me a wider scope to show my findings in an appealing way.
Ok, let’s cover this again : the files we need to invoke syntax highlighting total a minimum of seven files.
shCore.css – the foundation style markup for syntax highlighting
shCoreDefault.css – foundation coloring
shCoreMidnight.css – one of three theme support files, this theme is Midnight
shThemeDefault.css – a base theme with default values if no other theme chosen
shThemeMidnight.css – a color scheme for the shCoreMidnight.css theme
These files will need to be declared in your html page. See my example in next post. Here is a squint at the html markup for that example page :
To Recap :
IN part two, we’ll explore further requirements to make this all work.