unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dan Espen <despen@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Caps-mode vs. Overwrite mode
Date: Fri, 03 Apr 2015 11:14:43 -0400	[thread overview]
Message-ID: <mfmand$ncv$1@dont-email.me> (raw)
In-Reply-To: mfm93h$fdk$2@dont-email.me

Dan Espen <despen@verizon.net> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> When I toggle caps-mode on, overwrite mode stops working.
>>> That is, inserted characters insert instead of overwriting.
>>> Any hints?
>>
>> The caps-mode.el that's in GNU ELPA shouldn't suffer from this
>> problem, AFAIK.
>
> My first search only turns up caps-lock.el?
>
> Works better than caps-mode, but does type lower case
> when the shift key is used.  I can live with that I think,
> might even learn to like it.
>
> So, good enough, thanks!

Spoke too soon.
caps-lock mode isn't buffer local.

I want to turn this on only in selected buffers.

It looks like I have to toggle caps-lock mode off to enter
lower case commands in the mini-buffer.

I'm using this for editing HLASM, PL/I, etc, languages that
are traditionally done all upper case.

-- 
Dan Espen


  parent reply	other threads:[~2015-04-03 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 14:21 Caps-mode vs. Overwrite mode Dan Espen
2015-04-03 14:35 ` Stefan Monnier
     [not found] ` <mailman.3242.1428071743.31049.help-gnu-emacs@gnu.org>
2015-04-03 14:47   ` Dan Espen
2015-04-03 15:10     ` Eli Zaretskii
2015-04-03 15:25       ` Eli Zaretskii
2015-04-03 15:14     ` Dan Espen [this message]
     [not found]     ` <mailman.3243.1428073855.31049.help-gnu-emacs@gnu.org>
2015-04-03 15:21       ` Dan Espen
2015-04-03 15:26     ` Stefan Monnier
     [not found]     ` <mailman.3246.1428074815.31049.help-gnu-emacs@gnu.org>
2015-04-03 16:35       ` Dan Espen
2015-04-03 16:44         ` Stefan Monnier
     [not found]         ` <mailman.3250.1428079480.31049.help-gnu-emacs@gnu.org>
2015-04-03 17:10           ` Dan Espen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='mfmand$ncv$1@dont-email.me' \
    --to=despen@verizon.net \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).