From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 2LJZBzQUsV93HgAA0tVLHw (envelope-from ) for ; Sun, 15 Nov 2020 11:42:44 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id 6OMcAzQUsV/ASgAAbx9fmQ (envelope-from ) for ; Sun, 15 Nov 2020 11:42:44 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 51F1194051B for ; Sun, 15 Nov 2020 11:42:43 +0000 (UTC) Received: from localhost ([::1]:39692 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1keGQa-0004Lp-Kb for larch@yhetil.org; Sun, 15 Nov 2020 06:42:40 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:57770) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keGQ8-0004JU-2F for emacs-orgmode@gnu.org; Sun, 15 Nov 2020 06:42:12 -0500 Received: from mail-pl1-x632.google.com ([2607:f8b0:4864:20::632]:36518) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1keGQ5-0001hw-P6 for emacs-orgmode@gnu.org; Sun, 15 Nov 2020 06:42:11 -0500 Received: by mail-pl1-x632.google.com with SMTP id k7so6732737plk.3 for ; Sun, 15 Nov 2020 03:42:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:subject:in-reply-to:message-id:date :mime-version; bh=jZl0hplpJdbNf0Imh1ygR5wNjOepsGlZwcIr3xOApYc=; b=Z3LerulI53Sc4QSbDP2X7wppGyeswRWMSZfHSWzKkezn3bIV99ybiAsLkogQ06wd4r WAvE5mhbfKu2Rp7NHcrHO14eLCVI3PM2IR8gnaUMSIdm43h7aqDqIIeKRAtYn0pBQLXX qwMdqc7wOBbbADv0Yva5ssptsJLLL0RykQ621NQ6E9PHgqRSeJ/Y4xPcW7qVPmZ3TuIR p2PXXE7p811MWb05HYJg24LFRMLO84lR8FWwHeZVmCwDKtDUVzKocwfvr60vbPf/ZAML utNZF+m+I5C6G2E14SC0Q15ot+BrFfferfISHcTrElTI6f/hRjYdAlFmdRyItlBvIDqB D1lA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:subject :in-reply-to:message-id:date:mime-version; bh=jZl0hplpJdbNf0Imh1ygR5wNjOepsGlZwcIr3xOApYc=; b=qkcF/vVUzL18IulPZMil8GeozU1EF+axAQAOELRjYj1dsp4+E5x0WF1Qn1KTmCC7bP MB3xWMUs7ZEwyxivjP5vykWIOKnpDkfANqKtyfopFxcpOkEyNwREYNPyl7VolWhLy8Qv MmZJPn4rIl7Xai+jfgZ97s+fKcW9+jaxl5ggpkNG6UzzbsC+W/c5GS5R0T0c/E3M63RT DuAraa/dkNpPU/VSuAZ4/ePJPjIdv4ZGIJodsFR9y1sebJtz1ewrAZdFOGt71Lh6cI93 qLipNXsfbko+JHjQqK5kDnt/bk4G/M1LhwlMO9q/ereTT3OD2fvy+19V4lF1vKgyApXH jzQA== X-Gm-Message-State: AOAM530TbyuoqHG+BvOUxLVSto5nSdzh0/b3YVbQigqUPTnC4UrB23w/ QWIViH91mnZwTSWIiQ+H3aW4fc559nBGbw== X-Google-Smtp-Source: ABdhPJwb/dEpR8VupVOgy88IhHwylfkQ/loxpHXi0sltwx0BU6BLk8Sb99wSHR9xI+un4k5k0ohqfQ== X-Received: by 2002:a17:902:9a46:b029:d6:f20a:83e1 with SMTP id x6-20020a1709029a46b02900d6f20a83e1mr9031722plv.49.1605440526972; Sun, 15 Nov 2020 03:42:06 -0800 (PST) Received: from tim-desktop (106-69-127-65.dyn.iinet.net.au. [106.69.127.65]) by smtp.gmail.com with ESMTPSA id 145sm13431721pga.11.2020.11.15.03.42.05 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 15 Nov 2020 03:42:06 -0800 (PST) References: <665024.1605436621@apollo2.minshall.org> User-agent: mu4e 1.5.7; emacs 27.1.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: Changed list indentation behavior: how to revert? In-reply-to: <665024.1605436621@apollo2.minshall.org> Message-ID: <87ima67sol.fsf@gmail.com> Date: Sun, 15 Nov 2020 22:42:02 +1100 MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::632; envelope-from=theophilusx@gmail.com; helo=mail-pl1-x632.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=Z3LerulI; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -0.71 X-TUID: RfQ6shOlGhS7 Greg Minshall writes: > hi, all. > > David Rogers wrote: > >> Am I crazy to say that your last example of unwanted behavior is >> easier for me to read and understand? (and to me the common >> indenting is a hopeless mess?) > > yes, in fact, the "new" way sort of has the buffer indentation match > that of the outline structure of the file (specified by asterisks). > there's a lot to be said for that. (though, obviously, it's not what > everyone would want.) > > if the new mode stays as the standard, maybe we'd want to capture an > asterisk typed immediately after a newline that would (by default), put > that line-beginning asterisk back in column one? > I think this would be a great improvement. It is probably more comon that that when you type an asterisk as the first character in the line you want it to be a header and therefore, in the first column. On rare occasions when you do want an asterisk at the beginning of the line, you can indent it manually. > otherwise, this is what one gets (without remembering to do a C-j > instead of ): > ----- > * i wanted a headline > * i wanted a subhead, but it's ignored by org mode > ----- > which is maybe not optimal? > > in most non-org modes (including in Org Src... buffers, and in org files > when writing org-mode lists), i'm a big fan of electric indent mode. > > maybe an org-specific setting, "org-file-indent-follows-structure"? if > true, it means the user wants to have a "raw" org document laid out > according to the outline structure of the document. if false, it means > one, in general, wants the org file laid out with left-alignment (or, > right, in right-to-left) languages (not including embedded lists, and > whatever else i might be ignoring). > Seems like a reasonable approach to me. -- Tim Cross