emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ypo <ypuntot@gmail.com>
To: 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: Sun, 26 Jun 2022 21:26:36 +0200	[thread overview]
Message-ID: <281a29d8-8dfc-86b2-bc57-a6b0d5d338a1@gmail.com> (raw)
In-Reply-To: <62b8af84.1c69fb81.e0ca7.9738SMTPIN_ADDED_MISSING@mx.google.com>

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

Thanks, Bruno

I will save your advice for future debugging :-)

> Maybe you could use the keys that are already defined by org, to move
> between list items ?
>
>
>      ‘S-<UP>’
>      ‘S-<DOWN>’
>           Jump to the previous/next item in the current list, but only if
>           ‘org-support-shift-select’ is off(6).  If not, you can still use
>           paragraph jumping commands like ‘C-<UP>’ and ‘C-<DOWN>’ to quite
>           similar effect.

That requires me to change hands position, I must think about it.

Best regards :-)

El 26/06/2022 a las 21:13, Bruno Barbier escribió:
> Ypo<ypuntot@gmail.com>  writes:
>
>> Thanks, Bruno
>>
>> I've debugged it manually because (keymap-lookup) doesn't seem to exist
>> in my emacs, if that's possible.
> Sorry, my bad. 'keymap-lookup' will only exist in 29.  I should have
> used 'lookup-key':
>
>       (lookup-key global-map (kbd "C-u"))
>       
>> The problem comes from:
>>
>> (define-key org-mode-map (kbd "C-u C-n") #'org-next-item)
>>
>> If I eval that line, "C-u C-SPC" stops working on org-mode.
>>
>> Same problem in runemacs -q. Is it a bug?
> That line is the problem. It's hiding the real "C-u"
> (universal-argument) in org-mode buffers. Once you've lost the standard
> meaning of "C-u", you can't use C-u C-SPC and all other functions.
>
> Maybe you could use the keys that are already defined by org, to move
> between list items ?
>
>
>      ‘S-<UP>’
>      ‘S-<DOWN>’
>           Jump to the previous/next item in the current list, but only if
>           ‘org-support-shift-select’ is off(6).  If not, you can still use
>           paragraph jumping commands like ‘C-<UP>’ and ‘C-<DOWN>’ to quite
>           similar effect.
>
> Bruno
>
>
>>
>> El 25/06/2022 a las 9:47, Bruno Barbier escribió:
>>> Hi Ypo,
>>>
>>> Ypo<ypuntot@gmail.com>   writes:
>>>
>>>> Hi, Bruno
>>>>
>>>> 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"))
>>>>
>>> I'm not sure in what way it didn't work and I didn't try bug-hunter yet.
>>>
>>>
>>> FWIW, just in case it might help you, when I have such a problem, I just
>>> define a function, something like:
>>>
>>>      (defun my-check-bug ()
>>>        "Throw an error when C-u is not the universal argument in org-mode."
>>>        (with-temp-buffer
>>>          (org-mode)
>>>          (unless (eq 'universal-argument (keymap-lookup global-map "C-u"))
>>>            (error "C-u has been redefined"))))
>>>
>>>
>>> Then I add:
>>>
>>>      (my-check-bug)
>>>      
>>> everywhere in my init files and I start emacs with --debug-init.
>>>
>>> Good luck,
>>>
>>> Bruno
>>>
>>>

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

  parent reply	other threads:[~2022-06-26 19:28 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
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 [this message]
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=281a29d8-8dfc-86b2-bc57-a6b0d5d338a1@gmail.com \
    --to=ypuntot@gmail.com \
    --cc=brubar.cs@gmail.com \
    --cc=emacs-orgmode@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.
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).