From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: Cask-initialize messes up org table manipulation commands Date: Wed, 28 Sep 2016 22:53:01 -0500 Message-ID: <87d1jn9xb6.fsf@alphapapa.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpSPS-0000zH-H1 for emacs-orgmode@gnu.org; Wed, 28 Sep 2016 23:53:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpSPM-0005sk-JC for emacs-orgmode@gnu.org; Wed, 28 Sep 2016 23:53:21 -0400 Received: from [195.159.176.226] (port=58933 helo=blaine.gmane.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpSPM-0005rv-Ci for emacs-orgmode@gnu.org; Wed, 28 Sep 2016 23:53:16 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1bpSPF-0007qw-GF for emacs-orgmode@gnu.org; Thu, 29 Sep 2016 05:53:09 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Heikki Lehvaslaiho writes: > The cell content disappears but to my surprise the cursor jumped out > of the table! Trying with different tables, it came clear that the > cursor always jumped one line down and left of the table). (Under the > left border if you have a box cursor.) That should not happen! This may not be much help, because I'm still using Org 8.2.4, but I tried and was unable to reproduce this; the cursor remains in the table. > The final twist to this story is that if I start emacs, create an org > buffer with a table, and run org-table-cut-region key combination > first before evaling the init.el content, the cursor behaviour does > not change even after cask has been initialized! You said you bisected your init file; I assume you used the bug-hunter package? If by chance you did it manually instead, I would recommend doing it again with bug-hunter; maybe you made a tiny mistake that threw the whole thing off. :) Since it doesn't happen with "emacs -Q", I guess it must be someting in your config. (Though you might test with "emacs -q" also--there is a difference.) I don't use Cask, so I can't help you much there. What follows is what may be considered an unhelpful suggestion, but it's the best idea I have: switch from Cask/Pallet to use-package; it may give you finer-grained control over your init file, and bisecting may work better. I don't know remember how Cask works exactly, but if cask-initialize "monolithically" loads all the packages you have configured, I'm guessing you won't be able to bisect within it to figure out which package is causing the problem. Hope this helps.