Talk:Scroll-Wheel Copy and Paste

From OLPC
Revision as of 17:51, 17 September 2008 by 76.115.84.114 (talk) (I do NOT want the article page deleted.)
Jump to: navigation, search

I reorganized this a bit. I want to make sure that the "dummy" approach is right up top for folks who don't want to be messing around with scripts or remapping buttons. I also just linked to the instructions for the script on the other page.Tdang 06:14, 18 May 2008 (EDT)

uh, I don't have any idea of what you are "talking" about. Was the article page changED (past tense)? Then I would say the above paragraph belongs in the summary of your edits. The article page can easily be edited and re-arranged without ever looking at this page, making the above paragraph very confusing, possibly already the case. I don't know what you mean by the "dummy" approach. I don't know what you mean by "the script", or "the other page".

Anyways, I am here editing TALK because the article page said it has been proposed that it be deleted. I got to it from a clicking on a link in http://wiki.laptop.org/go/Terminal_Activity. That link will break. I do not see a replacement page. It would be a very bad idea to delete it without a replacement page. It says something like {{{{Link}}} but it is not a link, I click on it and nothing happens. So, until that has been fixed for some period of time, do not delete the main page.

Why is it being proposed for deletion? Because "Update 1" made it obsolete? How do I know if I have update 1 or not? I am very tired of updates, releases, etc. using different terminology every **** time. Sometimes it is ship.2, sometimes Release 8.1.0, sometimes by the build. I have build 656 and need SOME of the info for workarounds. However, a lot of stuff works for me that did not work with the first G1G1 that were shipped. When getting lost in wiki, I hardly ever know if what I am reading applies to my build. Sometimes even within a paragraph one thing is true for my release and then the next line not.

I understand there needs to be two numbers, ONE for software (and I don't understand why that can't be build number) and one for firmware; I do not understand why the user needs to know any more than that. Please keep in mind there are going to be getting xo's new in the future, heck they may received used ones as gifts. When wandering this "documentation" one should quickly easily know if what the are reading applies to them, heck they should be be able to constrain their search to get only results relevant to the builds(s) they specify.

I remapped my buttons and I find that much more convenient EVERYWHERE, not just in terminal. Just highlight and click, not highlight, ctl-c, click, ctl-v, when that works. 76.115.84.114 21:51, 17 September 2008 (UTC)