'less' width issuesWhen a command is over half the terminal size it breaksOutput visual (ASCII) Debian...
Windows OS quantum vs. SQL OS Quantum
date -d 'previous Monday" to display the preceding Monday
Was the Highlands Ranch shooting the 115th mass shooting in the US in 2019
How to slow yourself down (for playing nice with others)
Examples where existence is harder than evaluation
Which other programming languages apart from Python and predecessor are out there using indentation to define code blocks?
Why should password hash verification be time constant?
What do "KAL." and "A.S." stand for in this inscription?
Why does it take longer to fly from London to Xi'an than to Beijing
Is it a good idea to copy a trader when investing?
Renting a house to a graduate student in my department
Why is PerfectForwardSecrecy considered OK, when it has same defects as salt-less password hashing?
A Cunning Riley Riddle
How to get the IP of a user who executed a command?
How to efficiently lower your karma
Improving Sati-Sampajañña (situative wisdom)
Thesis' "Future Work" section – is it acceptable to omit personal involvement in a mentioned project?
What does this quote in Small Gods refer to?
How to get a ellipse shaped node in Tikz Network?
Passport stamps art, can it be done?
Are there variations of the regular runtimes of the Big-O-Notation?
Cryptography and elliptic curves
How to evaluate sum with one million summands?
What's the difference between const array and static const array in C/C++
'less' width issues
When a command is over half the terminal size it breaksOutput visual (ASCII) Debian dependency tree to terminal?Shift-Space in lessHow does less know the terminal resolution?less '+>' /path/to/fileset tab width for less outputLess quit behaviorTelnet equivalent for USB connected devices?Difference between less -r and less -RCustom terminal with less
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm connecting to my Linux boxes (primarily Debian Squeeze) using Putty for Windows. Whenever I run a 'less' command, e.g. on an aptitude search, less truncates the listing to much less than my window size. I've looked to see how I can override this but haven't come up with anything.
terminal less putty aptitude
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
add a comment |
I'm connecting to my Linux boxes (primarily Debian Squeeze) using Putty for Windows. Whenever I run a 'less' command, e.g. on an aptitude search, less truncates the listing to much less than my window size. I've looked to see how I can override this but haven't come up with anything.
terminal less putty aptitude
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
add a comment |
I'm connecting to my Linux boxes (primarily Debian Squeeze) using Putty for Windows. Whenever I run a 'less' command, e.g. on an aptitude search, less truncates the listing to much less than my window size. I've looked to see how I can override this but haven't come up with anything.
terminal less putty aptitude
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
I'm connecting to my Linux boxes (primarily Debian Squeeze) using Putty for Windows. Whenever I run a 'less' command, e.g. on an aptitude search, less truncates the listing to much less than my window size. I've looked to see how I can override this but haven't come up with anything.
terminal less putty aptitude
terminal less putty aptitude
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
edited 3 hours ago
Rui F Ribeiro
42.7k1486146
42.7k1486146
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
asked Apr 15 '11 at 17:55
Larry G. WapnitskyLarry G. Wapnitsky
14815
14815
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
What terminal is putty reporting to your linux boxes? echo $TERM to find out. You might try setting this to xterm-color (can be set in the putty session configs) for best results. Several character and behavior issues get straightened out when it thinks you have a capable terminal.
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
I'll have to check that when I get back to my office tomorrow. I'll keep you posted.
– Larry G. Wapnitsky
Apr 17 '11 at 19:05
add a comment |
Are you sure it's less doing the truncation and not aptitude? I notice that aptitude truncates to 80 columns by default when you redirect its output. Try aptitude search foo | cat and see if your output is truncated.
When you filter the output of a command, it's debatable whether it's best to truncate at the terminal width, at 80 columns or not at all. In fact the command can't know whether its output is eventually going to the terminal, so truncating to the terminal width is dubious.
You can run aptitude --disable-columns to make aptitude not truncate at all, but it won't align its output either. If your shell is bash or zsh, you can obtain the terminal width from the COLUMNS shell variable and pass it to aptitude:
aptitude -w $COLUMNS search foo |less
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
1
that's the exact thing. Passing $COLUMNS bypasses the issue (even locally). --disable-columns is too messy to look at. Time to create more aliases :)
– Larry G. Wapnitsky
Apr 17 '11 at 19:04
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f11397%2fless-width-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
What terminal is putty reporting to your linux boxes? echo $TERM to find out. You might try setting this to xterm-color (can be set in the putty session configs) for best results. Several character and behavior issues get straightened out when it thinks you have a capable terminal.
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
I'll have to check that when I get back to my office tomorrow. I'll keep you posted.
– Larry G. Wapnitsky
Apr 17 '11 at 19:05
add a comment |
What terminal is putty reporting to your linux boxes? echo $TERM to find out. You might try setting this to xterm-color (can be set in the putty session configs) for best results. Several character and behavior issues get straightened out when it thinks you have a capable terminal.
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
I'll have to check that when I get back to my office tomorrow. I'll keep you posted.
– Larry G. Wapnitsky
Apr 17 '11 at 19:05
add a comment |
What terminal is putty reporting to your linux boxes? echo $TERM to find out. You might try setting this to xterm-color (can be set in the putty session configs) for best results. Several character and behavior issues get straightened out when it thinks you have a capable terminal.
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
What terminal is putty reporting to your linux boxes? echo $TERM to find out. You might try setting this to xterm-color (can be set in the putty session configs) for best results. Several character and behavior issues get straightened out when it thinks you have a capable terminal.
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
answered Apr 15 '11 at 17:59
CalebCaleb
52.1k9153195
52.1k9153195
I'll have to check that when I get back to my office tomorrow. I'll keep you posted.
– Larry G. Wapnitsky
Apr 17 '11 at 19:05
add a comment |
I'll have to check that when I get back to my office tomorrow. I'll keep you posted.
– Larry G. Wapnitsky
Apr 17 '11 at 19:05
I'll have to check that when I get back to my office tomorrow. I'll keep you posted.
– Larry G. Wapnitsky
Apr 17 '11 at 19:05
I'll have to check that when I get back to my office tomorrow. I'll keep you posted.
– Larry G. Wapnitsky
Apr 17 '11 at 19:05
add a comment |
Are you sure it's less doing the truncation and not aptitude? I notice that aptitude truncates to 80 columns by default when you redirect its output. Try aptitude search foo | cat and see if your output is truncated.
When you filter the output of a command, it's debatable whether it's best to truncate at the terminal width, at 80 columns or not at all. In fact the command can't know whether its output is eventually going to the terminal, so truncating to the terminal width is dubious.
You can run aptitude --disable-columns to make aptitude not truncate at all, but it won't align its output either. If your shell is bash or zsh, you can obtain the terminal width from the COLUMNS shell variable and pass it to aptitude:
aptitude -w $COLUMNS search foo |less
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
1
that's the exact thing. Passing $COLUMNS bypasses the issue (even locally). --disable-columns is too messy to look at. Time to create more aliases :)
– Larry G. Wapnitsky
Apr 17 '11 at 19:04
add a comment |
Are you sure it's less doing the truncation and not aptitude? I notice that aptitude truncates to 80 columns by default when you redirect its output. Try aptitude search foo | cat and see if your output is truncated.
When you filter the output of a command, it's debatable whether it's best to truncate at the terminal width, at 80 columns or not at all. In fact the command can't know whether its output is eventually going to the terminal, so truncating to the terminal width is dubious.
You can run aptitude --disable-columns to make aptitude not truncate at all, but it won't align its output either. If your shell is bash or zsh, you can obtain the terminal width from the COLUMNS shell variable and pass it to aptitude:
aptitude -w $COLUMNS search foo |less
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
1
that's the exact thing. Passing $COLUMNS bypasses the issue (even locally). --disable-columns is too messy to look at. Time to create more aliases :)
– Larry G. Wapnitsky
Apr 17 '11 at 19:04
add a comment |
Are you sure it's less doing the truncation and not aptitude? I notice that aptitude truncates to 80 columns by default when you redirect its output. Try aptitude search foo | cat and see if your output is truncated.
When you filter the output of a command, it's debatable whether it's best to truncate at the terminal width, at 80 columns or not at all. In fact the command can't know whether its output is eventually going to the terminal, so truncating to the terminal width is dubious.
You can run aptitude --disable-columns to make aptitude not truncate at all, but it won't align its output either. If your shell is bash or zsh, you can obtain the terminal width from the COLUMNS shell variable and pass it to aptitude:
aptitude -w $COLUMNS search foo |less
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
Are you sure it's less doing the truncation and not aptitude? I notice that aptitude truncates to 80 columns by default when you redirect its output. Try aptitude search foo | cat and see if your output is truncated.
When you filter the output of a command, it's debatable whether it's best to truncate at the terminal width, at 80 columns or not at all. In fact the command can't know whether its output is eventually going to the terminal, so truncating to the terminal width is dubious.
You can run aptitude --disable-columns to make aptitude not truncate at all, but it won't align its output either. If your shell is bash or zsh, you can obtain the terminal width from the COLUMNS shell variable and pass it to aptitude:
aptitude -w $COLUMNS search foo |less
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
answered Apr 15 '11 at 19:05
GillesGilles
552k13211291637
552k13211291637
1
that's the exact thing. Passing $COLUMNS bypasses the issue (even locally). --disable-columns is too messy to look at. Time to create more aliases :)
– Larry G. Wapnitsky
Apr 17 '11 at 19:04
add a comment |
1
that's the exact thing. Passing $COLUMNS bypasses the issue (even locally). --disable-columns is too messy to look at. Time to create more aliases :)
– Larry G. Wapnitsky
Apr 17 '11 at 19:04
1
1
that's the exact thing. Passing $COLUMNS bypasses the issue (even locally). --disable-columns is too messy to look at. Time to create more aliases :)
– Larry G. Wapnitsky
Apr 17 '11 at 19:04
that's the exact thing. Passing $COLUMNS bypasses the issue (even locally). --disable-columns is too messy to look at. Time to create more aliases :)
– Larry G. Wapnitsky
Apr 17 '11 at 19:04
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f11397%2fless-width-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
