From: Ruijie Yu via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Pan Xie <xiepan@skyguard.com.cn>
Cc: emacs-orgmode@gnu.org
Subject: Re: [FR] Please add environment variable substitution in `org-display-inline-images'
Date: Sun, 28 May 2023 22:21:29 +0800 [thread overview]
Message-ID: <sdva5xotu3a.fsf@netyu.xyz> (raw)
In-Reply-To: <7a012430-6084-e693-1a86-f14d0512bebc@skyguard.com.cn>
Pan Xie <xiepan@skyguard.com.cn> writes:
> So my proposal of the code change would be (find "pxie" in the codes):
Thanks for proposing a change. It would be best if you produced a patch
file from this :) But someone with a bit more free time could do that as
well.
This is just FYI, and by no means a big deal, but it would become a huge
burden for the maintainers to apply the proposed changes if the
changeset becomes larger.
For future reference, I'm talking about something like this (assuming
you have git and a shell supporting IO redirect):
$ git diff this-file.el > something.diff
, or even better:
$ git commit -m commit-message...
$ git format-patch ...
In either case, you would attach the generated file in your message.
See also https://orgmode.org/worg/org-contribute.html for details.
--
Best,
RY
next prev parent reply other threads:[~2023-05-28 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 13:53 [FR] Please add environment variable substitution in `org-display-inline-images' Pan Xie
2023-05-28 14:21 ` Ruijie Yu via General discussions about Org-mode. [this message]
2023-05-31 8:24 ` Ihor Radchenko
2023-05-31 14:05 ` Pan Xie
2023-06-01 0:12 ` Samuel Wales
2023-06-01 0:24 ` Pan Xie
2023-06-01 8:20 ` [FR] Should we resolve environment variables in the file link path when exporting? (was: [FR] Please add environment variable substitution in `org-display-inline-images') Ihor Radchenko
2023-06-01 8:24 ` Pan Xie
2023-06-01 8:35 ` Ihor Radchenko
2023-06-01 8:38 ` Pan Xie
2023-06-01 8:52 ` Ihor Radchenko
2023-07-31 8:30 ` Ihor Radchenko
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=sdva5xotu3a.fsf@netyu.xyz \
--to=emacs-orgmode@gnu.org \
--cc=ruijie@netyu.xyz \
--cc=xiepan@skyguard.com.cn \
/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).