From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tilman Ahr Newsgroups: gmane.emacs.help Subject: Re: .emacs poser Date: Wed, 18 Dec 2013 03:25:16 +0100 Organization: A noiseless patient Spider Message-ID: <87eh5arj3n.fsf@ID-264037.user.dfncis.de> References: <87wqj4p720.fsf@nl106-137-194.student.uu.se> <87fvpsp3oy.fsf@nl106-137-194.student.uu.se> <8761qo56we.fsf@ID-264037.user.dfncis.de> <878uvjsa1k.fsf@nl106-137-194.student.uu.se> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1387333813 1170 80.91.229.3 (18 Dec 2013 02:30:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 Dec 2013 02:30:13 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 18 03:30:20 2013 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Vt6tt-00076R-9Z for geh-help-gnu-emacs@m.gmane.org; Wed, 18 Dec 2013 03:30:17 +0100 Original-Received: from localhost ([::1]:36649 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt6ts-0002rm-Pu for geh-help-gnu-emacs@m.gmane.org; Tue, 17 Dec 2013 21:30:16 -0500 X-Received: by 10.112.132.161 with SMTP id ov1mr1428437lbb.0.1387333606649; Tue, 17 Dec 2013 18:26:46 -0800 (PST) Original-Path: usenet.stanford.edu!w6no8922923wiw.0!news-out.google.com!h6ni10091wiy.1!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!195.62.100.242.MISMATCH!newsfeed.kamp.net!newsfeed.kamp.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 94 Injection-Info: mx05.eternal-september.org; posting-host="8d6d4e61d157ee96b57eb21196fd478f"; logging-data="1186"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18K1I5gf9GZgL5zZWW9yC+9jtc73FfSW9Q=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Cancel-Lock: sha1:aqICmRgXt6Px+JpykUxkI8DGjBM= sha1:WvRvGcT3FIQ9juVL1T1D5Eph2o0= Original-Xref: usenet.stanford.edu gnu.emacs.help:202803 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:95072 Archived-At: Emanuel Berg writes: > Tilman Ahr writes: [...] > but as for programming the US layout is 100 times > better. > > A couple of friends were telling me this for several > years. I always told them "I know the keys and > shortcuts on the Swedish keyboard. Why would I spend > time learning new?" But then I tried it *once* and > immediately understood. It is not about "other" keys > and shortcuts, it is about *better* keys and > shortcuts. For example, when doing C, on the US layout, > ';' is one key. On the Swedish ditto, it is *two*. You > don't have to write much more than a hello_word.c demo > to realize how much more pleasant it is not having to > do that extra hit at the end of every line. (And this > is just one example: there are also all the brackets.) I've never really viewed shifting as a seperate keystroke, but then I've never done whole lots of programming… >> I do have the „dead keys“ option enabled (to make >> typing the usual accents for french, at least, >> feasible without much ado) and remap CAPSLOCK[1] to >> the compose key, nonetheless. > > I also remapped caps to > > (defun buffer-menu-files-only () > (interactive) > (buffer-menu t) ) ;; files only Ok. I like having it as a compose key, because I need that somewhat frequently. It's done on a OS (GUI, really) level, so it works consistently in all my applications. I don't really use one so overwhelmingly much mort than the rest that it would make sense to have application-specific custon key-mapping. Might be different if I actually used my PC for work. >> Yes. Definitely. But there are (coff, coff) Operating >> Systems that make using a compose key hard, if not >> impossible... > > Yeah, like what? I never found a sane way to do it in Windows, for example. Might have gotten better in the last couple of years, though. My experience with Windows has been a while ago. [...] >>> Groff! Wow, you are a man (pun) of many >>> surprises. Is that used outside of the Unix manpages >>> world? >> >> It used to be. And I remember coming across a couple >> of projects where it was used to nicely format simple >> textual data in an automated way even a few years ago > > That's interesting, didn't know that. IIRC the rationale was that it did all the formatting needed for the task at hand, and was significantly simpler and less resource-hungry than LaTeX & Co. [...] >> Footnotes: [1] I have no idea why anybody would have >> a use for that key's original function on anything >> but a mechanic typewriter. Other than SHOUTING YOUR >> LUNGS OUT… > > *And* for #define C_CONSTANT and for non-parameters in > SQL (SELECT year ... ) - Alway used to just use the regular shift key for stuff like that, but then, as I stated earlier, I've never spend significant time programming. If you'd need to do a lot of that, CapsLock would surely be nice to have. > though when you think of it, that convention probably should be > dropped. There are quite a few conventions like that, when you really think about it. > It is just that your eyes are used it it, so it will be like teaching > an old dog how to sit. Something like that, yes.