emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Naoya Yamashita <conao3@gmail.com>
To: joaotavora@gmail.com
Cc: tkk@misasa.okayama-u.ac.jp, 45091@debbugs.gnu.org
Subject: bug#45091: 27.1; M-x org-table-paste-rectangle
Date: Sat, 16 Jan 2021 04:33:49 +0900 (JST)	[thread overview]
Message-ID: <20210116.043349.110178221913826662.conao3@gmail.com> (raw)
In-Reply-To: <CALDnm53Uv7tveRf508R7LWvoTbih27hNkj84Oad47o94NP1shw@mail.gmail.com>


> Okay, your bisect scripts points to one of my commits.
> 
> But I wish it was more automated.  Because I tried quite
> hard and sometimes I _could_ reproduce the problem and
> sometimes I couldn't.  So you could be seeing noise here.
> Maybe you can make your script  do those copy-paste
> operations automatically and reliably?  Then we'd be sure.
> 
> Anyway, I think is might be enough to point to a bug
> that was introduced by my commit, or rather exposed
> by it.  I'll have another look.

Sorry, you're true.  I try to build (semi-)automatically
reproduce step and do bisect with it, I got different commit.

It is 165f7383822086d465519ebe6e4283723923f097 (Update Org to 9.3).

(I wanted to reproduce the problem completely in auto, but the
problem is related to Emacs font-lock and post-command-hook, and
I could not reproduce it with --batch.  If you know how to
partially pass control to Emacs main-loop while running Elisp,
please tell me that.)


## Repro step

1. Prepare below contents.

```latex <~/dev/tmp/taks-file.tex>
-*- mode: latex -*-

| rownames                    |  acq |
| ref-coal-krt-2000-4-s1@4104 | 4104 |
| ref-coal-krt-2000-4-s1@4105 | 4105 |

|------------------------+--------+--------+---------------+---------+---------+-----+------+------|
|                        | 12C12C | 12C14N | 12C14Nz12C12C | d13Cion | d15Nion | N/C | d13C | d15N |
|------------------------+--------+--------+---------------+---------+---------+-----+------+------|
| !cniso-mtx-ogl1-2@4112 |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4113  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4114  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4115  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4116  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4117  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4118  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4119  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4124  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4125  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4126  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4127  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4128  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4129  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4130  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4131  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4132  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4133  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4134  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4135  |        |        |               |         |         |     |      |      |
| cniso-mtx-ogl1-2@4136  |        |        |               |         |         |     |      |      |
|------------------------+--------+--------+---------------+---------+---------+-----+------+------|
```

```sh <~/dev/tmp/bisect-script.sh>
git clean -fdx
make clean
./autogen.sh
./configure --prefix=$HOME/.local/head
make -j6
./src/emacs -Q ~/dev/tmp/taks-file.tex --eval "
  (progn
    (setq truncate-lines t)
    (setq debug-on-error t)
    (require 'org)
    (require 'org-table)
    (orgtbl-mode)
    
    (search-forward \"|\")
    (org-table-copy-region (1+ (org-table-begin)) (- (org-table-end) 2))
    
    (search-forward \"!\")
    
    (global-set-key (kbd \"<f5>\")
      (lambda ()
        (interactive)
        (org-table-paste-rectangle)
        (set-buffer-modified-p nil)
        (condition-case e
            (insert \"text\")
          (error
           (kill-emacs 1)))
        (kill-emacs 0)))
    )" \
2>/dev/null
```

2. Do below command in terminal
```sh
git bisect start emacs-27.1 emacs-26.3
git bisect run ~/dev/tmp/bisect-script.sh
```

3. Wait for build and wake Emacs, then press <f5>.

4. Got commit it has some problem.
(I got bellow bisect log in Magit)
```
Bisect Log (15)
git bisect start 'emacs-27.1' 'emacs-26.3'
git bisect good 38564f8a664347c42f7614d9c91e0d49e4a073e8
git bisect good 825fd4d34165e5edc718a9df93838a410d25ea81
git bisect good 5c5c1b559313d06aab6516ff1b1acf1da3a01c7d
git bisect bad d7cd4ab7d948427104003f1d35cf52a4eac45d0a
git bisect bad 4b2c2faab83fe3b13430b837be7d450b5cd47caf
git bisect good 16ce6dbef279bda70b4d60b4d2d0aff008bfa5f7
git bisect bad 5063e38921de8cb872965abda32bcc6fd8894532
git bisect bad 4c933077157ba409d645f4649c8a3a8e534d53d5
git bisect bad 096be9c4541329af259273fe604dc4f8669fbd8a
git bisect bad 8f2267c87bc96d6301aadeda66b870a61a0433e8
git bisect good 8bea7e9ab4453da71d9766d582089154f31de907
git bisect bad 165f7383822086d465519ebe6e4283723923f097
git bisect good 821de968434d2096bdea67dd24301bf6b517aef1
165f7383822086d465519ebe6e4283723923f097 is the first bad commit
```




      reply	other threads:[~2021-01-15 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m14kky8b2r.fsf@misasa.okayama-u.ac.jp>
     [not found] ` <831rg1aapc.fsf@gnu.org>
     [not found]   ` <CALDnm53uvZOy+KgTfFfiCZtSe8g-1+roC_pVC+dudHmK76S0VQ@mail.gmail.com>
     [not found]     ` <CALDnm53ZSJF8hCSKiaE5c=ykrTbnaxM9i5mtzpJHB-uP9M4=-Q@mail.gmail.com>
     [not found]       ` <m1ft4hyyw8.fsf_-_@misasa.okayama-u.ac.jp>
2020-12-08  2:42         ` João Távora
2020-12-08 17:02           ` João Távora
2020-12-08 17:08             ` Eli Zaretskii
2020-12-08 23:48             ` Tak Kunihiro
2020-12-20  0:14             ` Tak Kunihiro
2020-12-20  0:18               ` João Távora
2020-12-21  4:58                 ` Tak Kunihiro
2021-01-16  6:24               ` Tak Kunihiro
2021-01-15 11:44 ` Naoya Yamashita
2021-01-15 12:19   ` João Távora
2021-01-15 19:33     ` Naoya Yamashita [this message]

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=20210116.043349.110178221913826662.conao3@gmail.com \
    --to=conao3@gmail.com \
    --cc=45091@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=tkk@misasa.okayama-u.ac.jp \
    --subject='Re: bug#45091: 27.1; M-x org-table-paste-rectangle' \
    /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

Code repositories for project(s) associated with this 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).