From: "Sławomir Grochowski" <slawomir.grochowski@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] org-columns-edit-value will capitalize property
Date: Sun, 26 Mar 2023 08:42:18 +0200 [thread overview]
Message-ID: <CABnDLzEk+i8f94E-x4Nye4-UnkrnZ2VYhdDoEaMUEDvMS_B2cw@mail.gmail.com> (raw)
In-Reply-To: <CABnDLzEfMuv=2BadJQNNYiEWCYRmXeD4sVq0n27KDmdO2KRmCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
My apologies, I've made a mistake. There is not such a bug. Everythings
works correctly.
On Wed, 22 Mar 2023 at 13:18, Sławomir Grochowski <
slawomir.grochowski@gmail.com> wrote:
> Ok. I will try to send my first patch.
> Desired behavior is: by using command 'org-columns-edit-value' do not
> change 'property' name, just its value.
>
> On Wed, 22 Mar 2023 at 12:52, Ihor Radchenko <yantar92@posteo.net> wrote:
>
>> Sławomir Grochowski <slawomir.grochowski@gmail.com> writes:
>>
>> > After updating the value of property using command
>> 'org-columns-edit-value'
>> > it will capitalize the property name.
>> >
>> > As I understand, "Org is standardized on lower case"
>> > https://list.orgmode.org/87tuuw3n15.fsf@nicolasgoaziou.fr/.
>> >
>> > Is this a bug?
>>
>> This is for historical reasons.
>> Org supports (and will support) both, and we are slowly converting to
>> lower case.
>>
>> Patches welcome to change org-columns-edit-value.
>>
>> --
>> Ihor Radchenko // yantar92,
>> Org mode contributor,
>> Learn more about Org mode at <https://orgmode.org/>.
>> Support Org development at <https://liberapay.com/org-mode>,
>> or support my work at <https://liberapay.com/yantar92>
>>
>
[-- Attachment #2: Type: text/html, Size: 2323 bytes --]
prev parent reply other threads:[~2023-03-26 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 11:40 [bug] org-columns-edit-value will capitalize property Sławomir Grochowski
2023-03-22 11:54 ` Ihor Radchenko
2023-03-22 12:18 ` Sławomir Grochowski
2023-03-26 6:42 ` Sławomir Grochowski [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=CABnDLzEk+i8f94E-x4Nye4-UnkrnZ2VYhdDoEaMUEDvMS_B2cw@mail.gmail.com \
--to=slawomir.grochowski@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).