From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id EOpwHGaGS2La7AAAgWs5BA (envelope-from ) for ; Tue, 05 Apr 2022 01:59:34 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id oJu+FGaGS2KFLgAAG6o9tA (envelope-from ) for ; Tue, 05 Apr 2022 01:59:34 +0200 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 CE22512C28 for ; Tue, 5 Apr 2022 01:59:33 +0200 (CEST) Received: from localhost ([::1]:53622 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nbWbc-0006ND-Vr for larch@yhetil.org; Mon, 04 Apr 2022 19:59:33 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:53186) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nbWbA-0006Mn-QP for emacs-orgmode@gnu.org; Mon, 04 Apr 2022 19:59:04 -0400 Received: from mail-io1-xd30.google.com ([2607:f8b0:4864:20::d30]:33682) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nbWb9-0008Ni-2G for emacs-orgmode@gnu.org; Mon, 04 Apr 2022 19:59:04 -0400 Received: by mail-io1-xd30.google.com with SMTP id z6so13386014iot.0 for ; Mon, 04 Apr 2022 16:59:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=2cvGx5TN/kpQZJDXzRR3kV75c0AZGQdeBkKs+AIAE4g=; b=HmlK+iDN03hhXlBQ43Nz9G1RkfmXz4aoLYjMICvtoHKSQd5ZUDBprY1TKtwlNS8NTp dW8ciypjPUkmguZiW2JX1fQTAkN7j5BY36RicMYrxZ2F2VLnM/QNTh+pSTeuJEr3XsqM JE+lXDuTdWeSXjpREWsPFFGowO72EeMZVIPR73Aow2dOvdJDCpyScd8ulR1eg6F80HO5 pd+zj6IQTkC5CiWiYtWEtUXGYpn1Oqs/KgKq8p+Ya3XcdLt8eSYpee0+MESC90XDXxdT oVKCE2tn0FHesfMABh8iP3c9VE4GDFiFJ/bHQFL2cHz3tfslCqa2ob+cOKmdzFxxK9ow 5Jmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :mime-version; bh=2cvGx5TN/kpQZJDXzRR3kV75c0AZGQdeBkKs+AIAE4g=; b=bHjtrIzcvWMamZyAwadn5Yia0UY401/1ZEZUvxx9ck7byUWOxhEnk+SreGTd/WEZ4v 6O4qP4MpVYJBG/rTXqSPfUBMbRDPYwX/rmgQ6t0rRuu6eOTq0eld7RbXJkkU0/W6fWE5 MlZ9HuhYlLzTNc/WI8vM8a+6wdpndQp1Qh30yPQ3Dtyt9Cz0yi0irQnVdLsNqGiUWCkQ 0oUPzx3SHHjdivKZ9sAFXeP33cNsl1av0niBQrT0GKjTJzz1gL/no66QPWn11F76TKqi V4HZwqHkx8pon6gVvED1owaKUmonroIB+dS4fkYNe8fkdrXya/GBZWeu3IQRDb0Gm5U7 3apg== X-Gm-Message-State: AOAM533rnXLkIMCdB8ycGPif0txYjFmg2kYtQiHrB7MlmnYzCGIhaCzH jiwPREqYEbyWaHPGlT+bWvw+zR72GyM= X-Google-Smtp-Source: ABdhPJz2XBbesUKdfh+djYEgusdrM7Hb3TFeqj4/B8XSMQwdUMRH6+T8ey7SRbiuTrBMHlT2QaUvIQ== X-Received: by 2002:a02:cb0e:0:b0:321:34d7:a47f with SMTP id j14-20020a02cb0e000000b0032134d7a47fmr505273jap.50.1649116741138; Mon, 04 Apr 2022 16:59:01 -0700 (PDT) Received: from DM8P221MB0358.NAMP221.PROD.OUTLOOK.COM ([52.96.197.29]) by smtp.gmail.com with ESMTPSA id e17-20020a5d8ad1000000b00644d51bbffcsm7848352iot.36.2022.04.04.16.59.00 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Apr 2022 16:59:00 -0700 (PDT) From: jebb Bungo To: "emacs-orgmode@gnu.org" Subject: Re: org-return not being given 't' for INDENT parameter Thread-Topic: org-return not being given 't' for INDENT parameter Thread-Index: AQHYSH1UmkoKR4hk1kC/chQ+ZyYZSazgbeiX X-MS-Exchange-MessageSentRepresentingType: 1 Date: Mon, 4 Apr 2022 23:58:59 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 Content-Type: multipart/alternative; boundary="_000_DM8P221MB0358AF7D5900FE237A672C60AAE59DM8P221MB0358NAMP_" MIME-Version: 1.0 Received-SPF: pass client-ip=2607:f8b0:4864:20::d30; envelope-from=zixx999@gmail.com; helo=mail-io1-xd30.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 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-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1649116774; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=2cvGx5TN/kpQZJDXzRR3kV75c0AZGQdeBkKs+AIAE4g=; b=F1bPzNYyZdGO6FveU5FP7wG6aJihI+bwUcNwEoRwJWSsiBr/Kjglaj80Bp5QWK0kTAIDtL R+59ZvVV9M4SF3t8xZ9mNJ2Vow6kzLn2gVegISpaaHQnVFTX1a6rtprmKvU9qk+qOMkSzz zSzhU0fpysAPmoaicnvX630l6f1g8bLa17tjdaKAR3JwIGAyp5eUX2Kd46so/oh61F6w5I BRG+3YsxxuNMcIIwtgXTAomhuw5qKab9pLIiURk0kiRreTal3JjxwmTjzo7kRhG3/jS2WS 5MZcOoavbEp4CszKNRiB6NNkC59Ugvjfjs/mw7bYkZedGW0ps6wogoaE15JOgA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1649116774; a=rsa-sha256; cv=none; b=kZ5fICG+/wAdz2bLY2WMkjkC7Mpsr6Xp4wxlgSkuMXrrbpjHOEsLqDTgyNXn9Phc7qNd7e EI4ut4ASFR1L5d1fODT/lVx5zCx+2sAUBuFuys1d+8OlEK4Lla3qQ1rxYgxia8nOd0Ulso kNixotoQ5363OwswA3jHWvxlYF88foHZWbErnjQk7E11fN07QpJ7hhHZi8EryxhIlO1EeQ 3tvruSftTgVAMurgc72ogMLq0XIjqXNL7D8WfhBUKmFyPhPaZX5y+CZ9iC/A6yPIOnGLkQ BYHzVkCh6npwCxxb4bBpOH08yRjq4+qeSS0VlTYWt739tfKghyg9NaHnlXLS9A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=HmlK+iDN; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -8.88 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=HmlK+iDN; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: CE22512C28 X-Spam-Score: -8.88 X-Migadu-Scanner: scn0.migadu.com X-TUID: QQbrYW41m/Q1 --_000_DM8P221MB0358AF7D5900FE237A672C60AAE59DM8P221MB0358NAMP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: jebb Bungo Sent: Thu, 31 Mar 2022 10:14:43 -0400 To: ZIXX999@GMAIL.COM Subject: org-return not being given 't' for INDENT parameter Hello, I am having an odd behavior with org-return. I use hard indents, and I have= set 'org-adapt-indentation' to t in my .emacs file. However, I have notice= d that sometimes when I press RET under a heading, instead of getting an in= dent to match the indentation of the heading after the *'s, point is set ri= ght at 0. For example, the expected behavior of pressing RET at the end of = the line '* Heading' would be that point is placed on the next line below t= he heading, at column 2. I am having an issue pinpointing what is causing the error, however, as I h= aven't found any consistency. Sometimes RET works as expected in my files, = othertimes it does not. The bug does seem to only 'fix' in between instance= s of Emacs. I run Emacs as a daemon, and I noticed that sometimes the files= will work and other times not work, but only between instances of the daem= on/between system boots. I have tried restarting org mode through the menu-bar option "restart org-m= ode (new version)", as well as disabling and renabling org-mode, as well as= simply calling org-mode. No avail. When I tried to debug the function, I really didn't have a clue what I was = doing, but I think I narrowed the issue down to org-mode not getting the ri= ght context on where point is. I think this because org-return functions as= expected when called with 't' as an argument, such as (org-return t), but = I get the issue when calling just (org-return), which is bound to RET. My work-around, for the time being, has just been to disable electric-inden= t-mode, and use C-J to get the desired behavior, as that calls (org-return-= and-maybe-indent), and gives t if org-adapt-indentation is t and electric-i= ndent-mode is disabled. I apologize if my bug report is not up to scratch, but I have tried my best= to give as much detail as I can, and this is my first time trying a bug re= port, as I am unsure how to proceed with this on my own. Thank you, Kevan B. UPDATE: it seems to be caused by a double quote character. Upon continuing = to type my notes in my journal, I noticed that I had a quote and hit RET be= fore I remembered to close the quote, and suddenly RET worked as expected! = Then, after collecting my wits and after the end of my happy dance, I moved= point up and away, to the heading preceding the one I was working under, a= nd RET didn't indent properly. It seems that the open double quote might be masking the correct context. My apologies for not specifying originally, but I am on org 9.5.2 from melp= a, using emacs 27.2. --_000_DM8P221MB0358AF7D5900FE237A672C60AAE59DM8P221MB0358NAMP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
From: jebb Bungo <zixx999@gmail.com>
S= ent: Thu, 31 Mar 2022 10:14:43 -0400
To: ZIXX999@GMAIL.COM <zixx999@gmail.com>
Subject: org-return not being given 't' for INDENT paramet= er

Hello,

I am having an odd behavior with org-return. I use hard i= ndents, and I have set 'org-adapt-indentation' to t in my .emacs file. Howe= ver, I have noticed that sometimes when I press RET under a heading, instea= d of getting an indent to match the indentation of the heading after the *'s, point is set right at 0. For exa= mple, the expected behavior of pressing RET at the end of the line '* Headi= ng' would be that point is placed on the next line below the heading, at co= lumn 2.

I am having an issue pinpointing what is causing the erro= r, however, as I haven't found any consistency. Sometimes RET works as expe= cted in my files, othertimes it does not. The bug does seem to only 'fix' i= n between instances of Emacs. I run Emacs as a daemon, and I noticed that sometimes the files will work and ot= her times not work, but only between instances of the daemon/between system= boots.

I have tried restarting org mode through the menu-bar opt= ion "restart org-mode (new version)", as well as disabling and re= nabling org-mode, as well as simply calling org-mode. No avail.

When I tried to debug the function, I really didn't have = a clue what I was doing, but I think I narrowed the issue down to org-mode = not getting the right context on where point is. I think this because org-r= eturn functions as expected when called with 't' as an argument, such as (org-return t), but I get the issue when = calling just (org-return), which is bound to RET.

My work-around, for the time being, has just been to disa= ble electric-indent-mode, and use C-J to get the desired behavior, as that = calls (org-return-and-maybe-indent), and gives t if org-adapt-indentation i= s t and electric-indent-mode is disabled.

I apologize if my bug report is not up to scratch, but I = have tried my best to give as much detail as I can, and this is my first ti= me trying a bug report, as I am unsure how to proceed with this on my own.<= br>

Thank you,
Kevan B.



UPDATE: it seems to be caused by a double quote character. Upon continuing to type my notes in my journal, I noticed that I had a quo= te and hit RET before I remembered to close the quote, and suddenly RET wor= ked as expected! Then, after collecting my wits and after the end of my hap= py dance, I moved point up and away, to the heading preceding the one I was working under, and RET didn't inden= t properly. 

It seems that the open double quote might be masking the correct context.&n= bsp;

My apologies for= not specifying originally, but I am on org 9.5.2 from melpa, using emacs 2= 7.2.
--_000_DM8P221MB0358AF7D5900FE237A672C60AAE59DM8P221MB0358NAMP_--