emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ypo <ypuntot@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Bruno Barbier <brubar.cs@gmail.com>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: C-SPC works; C-u C-SPC doesn't. How could be?
Date: Sat, 25 Jun 2022 03:15:03 +0200	[thread overview]
Message-ID: <b131092e-c65d-1204-84f5-c4214e37ef18@gmail.com> (raw)
In-Reply-To: <87edzdv9zs.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

Hi Ihor.

elisp-bug-hunter sadly seems to have some bug, so I can't use it 
interactively anymore.

https://github.com/Malabarba/elisp-bug-hunter/issues/29

You are right, about the .org files though.

Thanks

El 25/06/2022 a las 2:53, Ihor Radchenko escribió:
> Ypo<ypuntot@gmail.com>  writes:
>
>> Yes, I tried your assertion for bug-hunter, but it didn't work.
>>
>> (unless (eq 'universal-argument (keymap-lookup global-map "C-u"))
>>          (error "C-u has been redefined"))
> You can also bisect interactively instead of using assertion.
> Note that your assertion is not expected to catch anything considering
> that the problem is only present inside .org files.
>
> Best,
> Ihor

[-- Attachment #2: Type: text/html, Size: 1628 bytes --]

  reply	other threads:[~2022-06-25  1:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  9:34 C-SPC works; C-u C-SPC doesn't. How could be? Ypo
2022-06-24 16:06 ` Greg Minshall
2022-06-25  0:49   ` Ypo
2022-06-24 17:31 ` Bruno Barbier
     [not found] ` <62b5f498.1c69fb81.8f12b.b976SMTPIN_ADDED_MISSING@mx.google.com>
2022-06-25  0:32   ` Ypo
2022-06-25  0:53     ` Ihor Radchenko
2022-06-25  1:15       ` Ypo [this message]
2022-06-25  3:28         ` Ihor Radchenko
2022-06-25  7:47     ` Bruno Barbier
     [not found]     ` <62b6bd46.1c69fb81.f4e75.9cf5SMTPIN_ADDED_MISSING@mx.google.com>
2022-06-26 17:22       ` Ypo
2022-06-26 19:13         ` Bruno Barbier
     [not found]         ` <62b8af84.1c69fb81.e0ca7.9738SMTPIN_ADDED_MISSING@mx.google.com>
2022-06-26 19:26           ` Ypo
2022-06-26 20:55         ` Tim Cross

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.orgmode.org/

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

  git send-email \
    --in-reply-to=b131092e-c65d-1204-84f5-c4214e37ef18@gmail.com \
    --to=ypuntot@gmail.com \
    --cc=brubar.cs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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/org-mode.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).