help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AUC-TeX completion fails to offer some possibilities


From: Matthias Rempe
Subject: Re: AUC-TeX completion fails to offer some possibilities
Date: 14 Dec 2002 01:00:04 +0100
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

>>>>> "DK" == David Kastrup <David.Kastrup@t-online.de> writes:

    > Matthias Rempe <mhrempe@web.de> writes:

    >> The reason is that no style hooks are applied. After saving and
    >> reloading the file the macros work.

    > That's what C-c C-n is for.

Uuhh, interesting. (Und wirste auch so alt wie 'ne Kuh,...) 
That keystrokes solve some of my problems, thank you. 

Just for curiosity: Why is TeX-normal-mode bound to two different
keys (C-c C-n and C-c #)?


-- 
Matthias
>From help-gnu-emacs-bounces@gnu.org  Fri Dec 13 19:00:13 2002
Path: 
shelby.stanford.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!170.207.51.80!not-for-mail
From: Kevin Rodgers <kevin.rodgers@ihs.com>
Newsgroups: gnu.emacs.help
Date: Fri, 13 Dec 2002 16:58:06 -0700
Lines: 43
Message-ID: <3DFA740E.4020408@ihs.com>
References: <mailman.148.1039707361.19936.help-gnu-emacs@gnu.org>
        <wkk7ida6q3.fsf@TheWorld.com> <sGtK9.31$n41.1147@paloalto-snr1.gtei.net>
NNTP-Posting-Host: 170.207.51.80
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: fu-berlin.de 1039823874 36857690 170.207.51.80 (16 [82742])
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US;
        rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2
X-Accept-Language: en-us
Xref: shelby.stanford.edu gnu.emacs.help:108120
To: help-gnu-emacs@gnu.org
Subject: Re: backward-delete-word?
X-BeenThere: help-gnu-emacs@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Users list for the GNU Emacs text editor <help-gnu-emacs.gnu.org>
List-Help: <mailto:help-gnu-emacs-request@gnu.org?subject=help>
List-Post: <mailto:help-gnu-emacs@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/help-gnu-emacs>,
        <mailto:help-gnu-emacs-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/help-gnu-emacs>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/help-gnu-emacs>,
        <mailto:help-gnu-emacs-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 14 Dec 2002 00:00:13 -0000

Barry Margolin wrote:

> In article <wkk7ida6q3.fsf@TheWorld.com>,
> Joe Fineman  <jcf@TheWorld.com> wrote:
> 
>>"Bingham, Jay" <Jay.Bingham@hp.com> writes:
>>
>>
>>>In similar circumstances I have stored text in a register and
>>>inserted it into the buffer from the register.
>>>
>>I too have often found registers a welcome relief from the
>>complexities of the kill ring.  However, there is one oddity about
>>their implementation that takes some getting used to.  When you insert
>>the contents of a register (C-x g), point is at the beginning of the
>>insertion; you have to do C-x C-x to get it to the end, where it would
>>be after yanking from the kill ring.  Either outcome could be argued
>>for, but it seems perverse to do these two very similar jobs in
>>different ways.
>>
> 
> I too have always found this curious.  My guess is that it's because
> registers are most often used in keyboard macros (if you think of a macro
> as a program, registers are the "variables"), while yanking is mainly
> interactive, and the designer of the register code didn't think the same
> expectations applied.  In any case, when creating a macro, it's easy to fix
> up the location after inserting a register, and then you don't have to
> worry about it.


C-x g runs the command insert-register-compatibility-binding:

Insert contents of register REGISTER.  (REGISTER is a character.)
Normally puts point before and mark after the inserted text.
If optional second arg is non-nil, puts mark before and point after.
Interactively, second arg is non-nil if prefix arg is supplied.


So: C-u C-x g

-- 
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;";>Kevin Rodgers</a>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]