<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar/9018390?origin\x3dhttp://7holybooks.blogspot.com', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

5.22.2011

Three lines for self-remembering

My four categories of self-remembering can really be three, because backlash is as much an event as any event of event self-remembering.

Therefore using rote, schedule, and backlash/event you can make the three lines of self-remembering effort.

When one line dies out another picks it up. For instance I find that as I've been approaching 12 noon for schedule self-remembering I am doing rote because the schedule effort has put me on watch.

We can't do rote forever, so when that one line of effort runs its course we can do schedule (which in a different yet real way keeps up the rote effort in an 'on watch' way). Then wanting to be awake in backlash/event creates a different line. All together we stay awake via the three lines of effort.