unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Slawomir Nowaczyk <slawomir.nowaczyk.847@student.lu.se>
Subject: Re: calc-dispatch problem
Date: Mon, 11 Sep 2006 21:20:45 +0200	[thread overview]
Message-ID: <20060911211209.2A2D.SLAWOMIR.NOWACZYK.847@student.lu.se> (raw)
In-Reply-To: <87lkoql2f9.fsf@vh213602.truman.edu>

On Mon, 11 Sep 2006 12:48:42 -0500
Jay Belanger <belanger@truman.edu> wrote:

#> Repeating the keys should start calc up normally.

It was also my impression -- but, as I have just noticed, neither doc
string nor manual say that explicitly (they only talk about specific
case of "*" key starting calc)... I think they should be changed to
specifically say that repeating key bound to calc-dispatch should work
even if it has been customised.

#> But `calc-dispatch' followed by "`" or "M-`" normally starts
#> calc-embedded-edit, and which behavior is used depends on whether or
#> not the `sit-for' is interrupted or not. If the `sit-for' is
#> interrupted, then a subsequent call of `this-command-keys' gets a
#> longer string than if `sit-for' isn't interrupted.

Thanks for the explanation.

#> I don't know what good the `sit-for' is doing; calc shouldn't behave
#> differently depending on how fast those keys are pressed.

I agree!

#> The behaviour without the `sit-for' seems the proper behaviour;
#> perhaps the `sit-for' should be removed.

Sounds good to me.

-- 
 Best wishes,
   Slawomir Nowaczyk
     ( slawomir.nowaczyk.847@student.lu.se )

Most common use of Brutal Sarcasm (tm) in Computer Science is:
  "It's a feature."

  reply	other threads:[~2006-09-11 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10 16:04 calc-dispatch problem Slawomir Nowaczyk
2006-09-10 18:19 ` David Kastrup
2006-09-10 19:11   ` Slawomir Nowaczyk
2006-09-10 20:05 ` Jason Rumney
2006-09-11 14:30   ` Slawomir Nowaczyk
2006-09-11 17:48   ` Jay Belanger
2006-09-11 19:20     ` Slawomir Nowaczyk [this message]
2006-09-12 18:27       ` Jay Belanger

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=20060911211209.2A2D.SLAWOMIR.NOWACZYK.847@student.lu.se \
    --to=slawomir.nowaczyk.847@student.lu.se \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).