From: Pete Williamson <petewil@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michal Nazarewicz <mina86@mina86.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] for review - Allow expansion of "~" (as opposed to "~user")
Date: Tue, 3 Mar 2015 10:38:42 -0800 [thread overview]
Message-ID: <CAHsSLHARsBtdG=4g=xkYybMtn4w0XB=km2vhG-pF1JbJkg+0pA@mail.gmail.com> (raw)
In-Reply-To: <83twy2orlg.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Yes, I mean make it an empty string. I'll send an updated patch.
Michael, is there still another issue I should solve if I make that
change? Thanks for all your help trying to get this figured out!
On Tue, Mar 3, 2015 at 10:36 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Tue, 3 Mar 2015 10:22:39 -0800
> > From: Pete Williamson <petewil@google.com>
> > Cc: Michal Nazarewicz <mina86@mina86.com>, emacs-devel@gnu.org
> >
> > So to solve my porting problem for NaCl, would it be best if I just did a
> > system check for NaCl, and if it is the current system, then clear the
> > "init-file-user" string?
>
> If by "clear" you mean make it an empty string, then yes, I think
> that's what you should do.
>
[-- Attachment #2: Type: text/html, Size: 1259 bytes --]
next prev parent reply other threads:[~2015-03-03 18:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 0:06 [PATCH] for review - Allow expansion of "~" (as opposed to "~user") Pete Williamson
2015-02-28 8:08 ` Eli Zaretskii
2015-03-02 9:44 ` Michal Nazarewicz
2015-03-02 13:50 ` Eli Zaretskii
2015-03-02 20:37 ` Michal Nazarewicz
2015-03-03 15:37 ` Eli Zaretskii
2015-03-03 17:48 ` Michal Nazarewicz
2015-03-03 18:09 ` Eli Zaretskii
2015-03-03 18:20 ` Eli Zaretskii
2015-03-03 18:22 ` Pete Williamson
2015-03-03 18:36 ` Eli Zaretskii
2015-03-03 18:38 ` Pete Williamson [this message]
2015-03-03 21:01 ` Michal Nazarewicz
2015-03-03 21:03 ` Michal Nazarewicz
2015-03-04 18:06 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHsSLHARsBtdG=4g=xkYybMtn4w0XB=km2vhG-pF1JbJkg+0pA@mail.gmail.com' \
--to=petewil@google.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mina86@mina86.com \
/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.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).