Skip to content
This repository was archived by the owner on May 11, 2025. It is now read-only.

Commit 2cc7bcd

Browse files
Remove obsolete .panel-body elements
Remove obsolete .panel-body elements We don't need them anymore in bootstrap 4. The same functionality has been replaced by .card-body
1 parent 65e0c27 commit 2cc7bcd

7 files changed

Lines changed: 748 additions & 955 deletions

File tree

compose-environments/index.html

Lines changed: 19 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -135,26 +135,23 @@ <h3>Tips and known issues</h3>
135135
</a>
136136
</div>
137137
<div id="collapse1" class="card-body collapse" role="tabpanel" aria-labelledby="heading1">
138-
<div class="panel-body">
139-
<p>
140-
Tmux starts the shells as loginshells, that means that for example bash is
141-
going to load the `profile` files. This sort of behaviour triggers the
142-
path_helper that will move our added PATH to the end. This is not the behaviour
143-
we want.
144-
</p>
145-
146-
<p>
147-
To fix this you can change the if for the path helper in your `/etc/profile` to
148-
the following:
149-
</p>
150-
151-
<pre>
138+
<p>
139+
Tmux starts the shells as loginshells, that means that for example bash is
140+
going to load the `profile` files. This sort of behaviour triggers the
141+
path_helper that will move our added PATH to the end. This is not the behaviour
142+
we want.
143+
</p>
144+
145+
<p>
146+
To fix this you can change the if for the path helper in your `/etc/profile` to
147+
the following:
148+
</p>
149+
150+
<pre>
152151
if [ -z $TMUX ] && [ -x /usr/libexec/path_helper ]; then
153152
eval `/usr/libexec/path_helper -s`
154153
fi
155154
</pre>
156-
157-
</div>
158155
</div>
159156
</div>
160157

@@ -166,14 +163,12 @@ <h3>Tips and known issues</h3>
166163
</a>
167164
</div>
168165
<div id="collapse2" class="card-body collapse" role="tabpanel" aria-labelledby="heading2">
169-
<div class="panel-body">
170-
<p>
171-
<a href="http://ohmyz.sh/">Oh-my-zsh</a> users should check if there is no fixed setting
172-
for <code>$PATH</code> in their <code>~/.zshrc</code>. If that is the case you can safely comment it
173-
out. If somewhere in your shell startup <code>$PATH</code> is forced you lose the features
174-
the <code>./environment</code> script brings to you.
175-
</p>
176-
</div>
166+
<p>
167+
<a href="http://ohmyz.sh/">Oh-my-zsh</a> users should check if there is no fixed setting
168+
for <code>$PATH</code> in their <code>~/.zshrc</code>. If that is the case you can safely comment it
169+
out. If somewhere in your shell startup <code>$PATH</code> is forced you lose the features
170+
the <code>./environment</code> script brings to you.
171+
</p>
177172
</div>
178173
</div>
179174

0 commit comments

Comments
 (0)