summaryrefslogtreecommitdiffstats
path: root/.dtprofile
blob: 79ec412108015e148c98a69fcd40c0b4155ba16f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
# ##########################################################################
# #
# #  .dtprofile
# #
# #  user personal environment variables
# #
# #  Common Desktop Environment (CDE)
# #
# #  (c) Copyright 1996 Digital Equipment Corporation.
# #  (c) Copyright 1993,1994,1996 Hewlett-Packard Company.
# #  (c) Copyright 1993,1994,1996 International Business Machines Corp.
# #  (c) Copyright 1993,1994,1996 Sun Microsystems, Inc.
# #  (c) Copyright 1993,1994,1996 Novell, Inc. 
# #  (c) Copyright 1996 FUJITSU LIMITED.
# #  (c) Copyright 1996 Hitachi.
# #
# #
# #  $TOG: dtprofile.src /main/5 1999/03/30 10:32:43 mgreess $
# #
# ##########################################################################


# ##########################################################################
# # 
# #  Your $HOME/.dtprofile is read each time you login to the Common Desktop
# #  Environment (CDE) and is the place to set or override desktop 
# #  environment variables for your session. Environment variables set in
# #  $HOME/.dtprofile are made available to all applications on the desktop.
# #  The desktop will accept either sh or ksh syntax for the commands in 
# #  $HOME/.dtprofile.
# # 
# ##########################################################################


# ##########################################################################
# #   
# #  Random stdout and stderr output from apps started by Session Mgr or
# #  by actions via front panel or workspace menu can be directed into 
# #  the user's $HOME/.dt/sessionlogs directory.  By default this output
# #  is not recorded.  Instead it is sent off to /dev/null (Unix's "nothing"
# #  device).
# #   
# #  If this random application output is wanted (usually only wanted for
# #  debugging purposes), commenting out following "dtstart_sessionlogfile"
# #  lines will send output to your $HOME/.dt/sessionlogs directory.
# #   
# #  Alternatively, can change "/dev/null" to "/dev/console" to see this
# #  debugging output on your console device.  Can start a console via the
# #  Workspace programs menu or via Application Mgr's Desktop Tools 
# #  "Terminal Console" icon. 
# #   
# ##########################################################################

echo "This session log file is currently disabled."  >  $dtstart_sessionlogfile
echo "To enable logging, edit $HOME/.dtprofile and"  >> $dtstart_sessionlogfile
echo "remove dtstart_sessionlogfile=/dev/null line." >> $dtstart_sessionlogfile

export dtstart_sessionlogfile="/dev/null"


# ##########################################################################
# #
# #  By default, the desktop does not read your standard $HOME/.profile
# #  or $HOME/.login files. This can be changed by uncommenting the
# #  DTSOURCEPROFILE variable assignment at the end of this file. The
# #  desktop reads .profile if your $SHELL is "sh" or "ksh", or .login
# #  if your $SHELL is "csh".
# #
# #  The desktop reads the .dtprofile and .profile/.login without an 
# #  associated terminal emulator such as xterm or dtterm. This means
# #  there is no available command line for interaction with the user.
# #  This being the case, these scripts must avoid using commands that
# #  depend on having an associated terminal emulator or that interact
# #  with the user. Any messages printed in these scripts will not be
# #  seen when you log in and any prompts such as by the 'read' command
# #  will return an empty string to the script. Commands that set a
# #  terminal state, such as "tset" or "stty" should be avoided.
# #
# #  With minor editing, it is possible to adapt your .profile or .login
# #  for use both with and without the desktop.  Group the statements not
# #  appropriate for your desktop session into one section and enclose them
# #  with an "if" statement that checks for the setting of the "DT"
# #  environment variable. When the desktop reads your .profile or .login
# #  file, it will set "DT" to a non-empty value for which your .profile or
# #  .login can test. 
# #   
# #  example for sh/ksh
# #  
# #    if [ ! "$DT" ]; then
# #      #
# #      # commands and environment variables not appropriate for desktop
# #      #
# #      stty ...
# #   tset ...
# #   DISPLAY=mydisplay:0
# #   ...
# #    fi	    
# #
# #    #
# #    # environment variables common to both desktop and non-desktop
# #    #
# #    PATH=$HOME/bin:$PATH
# #    MYVAR=value
# #    export MYVAR
# #    ...
# #	  
# #  example for csh
# #
# #    if ( ! ${?DT} ) then
# #      #
# #      # commands and environment variables not appropriate for desktop
# #      #
# #      stty ...
# #      tset ...
# #      setenv DISPLAY mydisplay:0
# #      ...
# #    endif
# #
# #    #
# #    # environment variables common to both desktop and non-desktop
# #    #
# #    setenv PATH $HOME/bin:$PATH
# #    setenv MYVAR value
# #    ...
# #  
# #  Errors in .dtprofile or .profile (.login) may prevent a successful
# #  login.  The login process scans .dtprofile and .profile (.login)
# #  for errors (using the '-n' option to the shell).  It avoids running
# #  them if errors are found and prints the errors to the
# #  $HOME/.dt/startlog file.  However, his process is not fool proof
# #  as some shells are better at finding errors thant others.
# #  If after you login, your session startup terminates and you
# #  are presented with the login screen, this might be the cause. If this
# #  happens, select the Options->Sessions->Failsafe Session item on the
# #  login screen, login and correct the error. The $HOME/.dt/startlog and
# #  $HOME/.dt/errorlog files may be helpful in identifying errors.
# #
# ##########################################################################

#
#  If $HOME/.profile (.login) has been edited as described above, uncomment
#  the following line.
#
# DTSOURCEPROFILE=true

export DTOPEN_VIMAGE="xv nsxiv display gimp"
export DTOPEN_VVIDEO="mpv"
export DTOPEN_VPS="gv"
export DTOPEN_VPDF="xpdf zathura"

startif() {
	pgrep "$1" >/dev/null || "$@" >/dev/null 2>&1 &
}


sysctl hw.snd.default_unit=4
pgrep musicpd >/dev/null || musicpd >/dev/null 2>&1
"$HOME"/.local/bin/kb
xset s off
xset -dpms
startif dunst
startif picom
startif lowbat
startif mpd-notification
startif xscreensaver --no-splash
# ekb
cd "$HOME"
xrdb "$HOME"/.config/x11/xresources
notify-send -u normal 'Welcome' "  Welcome back, partner\!"