zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: exec
Date: Mon, 3 Jun 2024 08:59:02 -0700	[thread overview]
Message-ID: <56b5ac4e-53b4-46e1-94f8-d70e07c741da@eastlink.ca> (raw)
In-Reply-To: <CAA=-s3zo=L7OcEFVhMMdZZgNmrEGOpnNgOh1SgCML2=YPJnYJQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]



On 2024-06-03 08:33, Mark J. Reed wrote:

> In X11 setups back in the day, it wasn't uncommon for the *.xinitrc* 
> or whatever startup file you use to end with something like *exec 
> xterm*, so if /that particular instance/ of *xterm* exited, then the 
> whole window system went away with it. But that's not typical of 
> modern systems. And even then the computer wouldn't shut down. You'd 
> just be dropped back at your original shell on the console, or if 
> you'd also *exec*'ed *xinit*, at a login prompt.
Exactly.  My point was rhetorical -- obviously control resumes 
'somewhere' in the stack of all these GUI functions.  But it isn't easy 
to figure out where.  I even tried this:

   # start xfce4-session normally
touch /aMisc/"$(date +%F--%T)-starting xfce"
#    exec xfce4-session
     xfce4-session
touch /aMisc/"$(date +%F--%T)-stopping xfce"

... just to see if I could get some sense of flow control, but it 
doesn't work.  I never get to 'stopping'.  It feels wrong.

[-- Attachment #2: Type: text/html, Size: 1611 bytes --]

  reply	other threads:[~2024-06-03 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 14:10 exec Ray Andrews
2024-06-03 14:17 ` exec Mark J. Reed
2024-06-03 14:42   ` exec Ray Andrews
2024-06-03 14:50     ` exec Eric Cook
2024-06-03 14:54     ` exec Mark J. Reed
2024-06-03 15:16       ` exec Mark J. Reed
2024-06-03 15:29         ` exec Ray Andrews
2024-06-03 15:22       ` exec Ray Andrews
2024-06-03 15:33         ` exec Mark J. Reed
2024-06-03 15:59           ` Ray Andrews [this message]
2024-06-03 16:06           ` exec Bart Schaefer
2024-06-03 16:23             ` exec Ray Andrews

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56b5ac4e-53b4-46e1-94f8-d70e07c741da@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).