[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Finding the dump
From: |
Stefan Monnier |
Subject: |
Re: Finding the dump |
Date: |
Sun, 27 Jan 2019 14:42:35 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> Sure, but such callers are holding it wrong. If you set argv[0] to some
> random string unrelated to Emacs, you break startup. That's fine.
Indeed, this is sufficiently rare in my experience that I wouldn't worry
about that case.
>>> every system I've seen. Here's the algorithm: look at argv[0]: if it's
>>> not an absolute path, make it absolute by prepending the startup CWD.
>> If the executable is found on $PATH then argv[0] is *not* relative to CWD.
> In that case, argv[0] will be absolute.
That's not what I'm seeing on my system.
When I type `emacs` into my shell (zsh under Debian), it is started with
`emacs` as argv[0] and not with an absolute file name.
Stefan
- Re: Finding the dump, (continued)
- Re: Finding the dump, Eli Zaretskii, 2019/01/27
- Re: Finding the dump, Andreas Schwab, 2019/01/27
- Re: Finding the dump, Eli Zaretskii, 2019/01/27
- Re: Finding the dump, Andreas Schwab, 2019/01/27
- Re: Finding the dump, Eli Zaretskii, 2019/01/27
- Re: Finding the dump, Andreas Schwab, 2019/01/27
- Re: Finding the dump, Daniel Colascione, 2019/01/27
- Re: Finding the dump, Andreas Schwab, 2019/01/27
- Re: Finding the dump, Stefan Monnier, 2019/01/27
- Re: Finding the dump, Daniel Colascione, 2019/01/27
- Re: Finding the dump,
Stefan Monnier <=
- Re: Finding the dump, Daniel Colascione, 2019/01/27
- Re: Finding the dump, Andreas Schwab, 2019/01/27
- Re: Finding the dump, Daniel Colascione, 2019/01/27
- Re: Finding the dump, Andreas Schwab, 2019/01/27
- Re: Finding the dump, Paul Eggert, 2019/01/27
- Re: Finding the dump, Daniel Colascione, 2019/01/27
- Re: Finding the dump, Paul Eggert, 2019/01/27
- Re: Finding the dump, Daniel Colascione, 2019/01/27
- Re: Finding the dump, Richard Stallman, 2019/01/28
- Re: Finding the dump, Paul Eggert, 2019/01/28