Show More
@@ -195,6 +195,7 b' even though stdout is no longer a tty.' | |||||
195 | paged! 'summary: modify a 8\n' |
|
195 | paged! 'summary: modify a 8\n' | |
196 | paged! '\n' |
|
196 | paged! '\n' | |
197 |
|
197 | |||
|
198 | #if no-chg | |||
198 | An invalid pager command name is reported sensibly if we don't have to |
|
199 | An invalid pager command name is reported sensibly if we don't have to | |
199 | use shell=True in the subprocess call: |
|
200 | use shell=True in the subprocess call: | |
200 | $ hg log --limit 3 --config pager.pager=this-command-better-never-exist |
|
201 | $ hg log --limit 3 --config pager.pager=this-command-better-never-exist | |
@@ -215,6 +216,17 b' use shell=True in the subprocess call:' | |||||
215 | date: Thu Jan 01 00:00:00 1970 +0000 |
|
216 | date: Thu Jan 01 00:00:00 1970 +0000 | |
216 | summary: modify a 8 |
|
217 | summary: modify a 8 | |
217 |
|
218 | |||
|
219 | #else | |||
|
220 | Currently, chg has its own runpager implementation, which does not show the | |||
|
221 | "missing pager" message. The error message is globed out since the shell could | |||
|
222 | print different message. | |||
|
223 | $ hg log --limit 3 --config pager.pager=this-command-better-never-exist | |||
|
224 | /bin/sh: this-command-better-never-exist: command not found (?) | |||
|
225 | * (glob) (?) | |||
|
226 | killed! | |||
|
227 | [255] | |||
|
228 | ||||
|
229 | #endif | |||
218 |
|
230 | |||
219 | A complicated pager command gets worse behavior. Bonus points if you can |
|
231 | A complicated pager command gets worse behavior. Bonus points if you can | |
220 | improve this. |
|
232 | improve this. |
General Comments 0
You need to be logged in to leave comments.
Login now