Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #202901
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: issues with stretch, issue 2 from many |
| Date | 2018-11-29 21:20 +0100 |
| Message-ID | <wZAWZ-6C0-3@gated-at.bofh.it> (permalink) |
| References | <wYLhL-7x1-5@gated-at.bofh.it> <wYOyZ-141-5@gated-at.bofh.it> <wYP21-1u0-5@gated-at.bofh.it> <wZeMN-L4-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed 28 Nov 2018 at 20:18:25 +0000, Brian wrote: > On Tue 27 Nov 2018 at 12:04:37 -0500, Greg Wooledge wrote: > > [...] > > > My understanding is .xsessionrc was created in order to give users a > > modicum of control over their own lives if they happen to use GNOME. > > It doesn't say that in #411639. > > [...] However: https://wiki.debian.org/Xsession says (referring to ~/xsessionrc) There are typically three kinds of commands you may wish to use in this file: * You may place environment variable definitions here, directly: export SOME_VAR="some value" This was the reason for ~/.xsessionrc coming into existence. * You may dot in some other POSIX shell configuration file: if [ -r ~/.profile ]; then . ~/.profile; fi A user can, but ~/xsessionrc wasn't invented for that. ~/.xsession was. * You may directly run X client programs: xclock -geometry +0+0 & A user can, but ~/.xsessionrc definitely wasn't devised for that. OTOH, ~/.xsession was. How does ~/.xsessionrc assume such importance over ~/.xsession in the grand scheme of X things? -- Brian
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
issues with stretch, issue 2 from many Ionel Mugurel Ciobîcă <I.M.Ciobica@gmail.com> - 2018-11-27 14:10 +0100
Re: issues with stretch, issue 2 from many David Wright <deblis@lionunicorn.co.uk> - 2018-11-27 17:40 +0100
Re: issues with stretch, issue 2 from many Greg Wooledge <wooledg@eeg.ccf.org> - 2018-11-27 18:10 +0100
Re: issues with stretch, issue 2 from many Brian <ad44@cityscape.co.uk> - 2018-11-28 21:40 +0100
Re: issues with stretch, issue 2 from many Greg Wooledge <wooledg@eeg.ccf.org> - 2018-11-29 21:20 +0100
Re: issues with stretch, issue 2 from many Brian <ad44@cityscape.co.uk> - 2018-11-29 21:50 +0100
Re: issues with stretch, issue 2 from many Brian <ad44@cityscape.co.uk> - 2018-11-29 21:20 +0100
Re: issues with stretch, issue 2 from many Brian <ad44@cityscape.co.uk> - 2018-11-27 20:00 +0100
Re: issues with stretch, issue 2 from many Greg Wooledge <wooledg@eeg.ccf.org> - 2018-11-30 16:30 +0100
Re: issues with stretch, issue 2 from many Ionel Mugurel Ciobîcă <I.M.Ciobica@gmail.com> - 2018-11-30 16:50 +0100
Re: issues with stretch, issue 2 from many Greg Wooledge <wooledg@eeg.ccf.org> - 2018-11-30 17:00 +0100
Re: issues with stretch, issue 2 from many Mark Fletcher <mark27q1@gmail.com> - 2018-11-30 17:30 +0100
Re: issues with stretch, issue 2 from many Brian <ad44@cityscape.co.uk> - 2018-11-30 17:40 +0100
Re: issues with stretch, issue 2 from many Ionel Mugurel Ciobîcă <I.M.Ciobica@gmail.com> - 2018-11-30 16:30 +0100
Re: issues with stretch, issue 2 from many Brian <ad44@cityscape.co.uk> - 2018-11-30 17:50 +0100
Re: issues with stretch, issue 2 from many Richard Hector <richard@walnut.gen.nz> - 2018-12-02 21:00 +0100
Re: issues with stretch, issue 2 from many David Wright <deblis@lionunicorn.co.uk> - 2018-12-06 16:50 +0100
Re: issues with stretch, issue 2 from many David Wright <deblis@lionunicorn.co.uk> - 2018-12-01 20:50 +0100
Re: issues with stretch, issue 2 from many Ionel Mugurel Ciobîcă <I.M.Ciobica@gmail.com> - 2018-12-11 14:30 +0100
csiph-web