{"id":14142,"date":"2026-05-20T03:00:00","date_gmt":"2026-05-20T07:00:00","guid":{"rendered":"https:\/\/www.both.org\/?p=14142"},"modified":"2026-05-02T20:19:18","modified_gmt":"2026-05-03T00:19:18","slug":"converting-tabs-to-spaces","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=14142","title":{"rendered":"Converting tabs to spaces"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n <\/span>\r\n<\/div><\/div>\n

You don’t have to go far in certain programming circles before you find the classic “tabs versus spaces” argument. Some people like to use tabs to provide indenting in their program source code; others live like animals and use spaces. You can see which side of the fence I live on.<\/p>\n\n\n\n

I’m joking! I might use tabs to indent my code when I’m working in the editor, then convert those tabs to spaces when I need to share my work with someone else. The indent<\/strong> program can reformat C source files, including changing tabs to spaces.<\/p>\n\n\n\n

But if you need to work with other files that aren’t source code, you need another tool. The expand<\/strong> command is a standard Unix program that should be available on every Linux system. This command converts tabs to spaces. For example, I often use expand<\/strong> if I need to display the contents of a file in an article or book chapter; those tabs can “get in the way” in a publishing system.<\/p>\n\n\n\n

Writing your own<\/h2>\n\n\n\n

If you’ve ever wondered how the expand<\/strong> program works, it’s not a very difficult program to write on your own. Writing your own version also means you can create a similar program for other operating systems that lack an expand<\/strong> command, such as DOS.<\/p>\n\n\n\n

Let’s call our program untab<\/strong> because it will convert tabs to spaces. The program only needs to track a few things: how “wide” is a tab, what column it’s printing to, and what character to print. In the simplest case, we can use a constant value for the tab width, as TABSIZE<\/code>:<\/p>\n\n\n\n

#define TABSIZE 8<\/code><\/pre>\n\n\n\n
The other values can be tracked as variables in a program: c<\/code> for the character to print, and col<\/code> for the column it’s printing to.<\/p>\n\n\n\n
    short col = TABSIZE;\n    int c;<\/code><\/pre>\n\n\n\n
We can get away with a short<\/code> variable type for the column, because it will only track values up to 8. However, the c<\/code> variable needs to be an int<\/code> because that’s how C reads characters one at a time from a file.<\/p>\n\n\n\n
The program can read a file one character at a time. As it prints each character, the program needs to track what column it’s in. This is just a matter of incrementing a counter, until the program encounters a tab. For a tab, it needs to expand the tab into spaces:<\/p>\n\n\n\n
    while ((c = getchar()) != EOF) {\n        if (c == '\\t') {\n            while (col > 0) {\n                putchar(' ');\n                col--;\n            }\n        }\n        else {\n            putchar(c);\n            col--;\n        }\n\n        if ((c == '\\n') || (col == 0)) {\n            col = TABSIZE;\n        }\n    }<\/code><\/pre>\n\n\n\n
Actually, the program doesn’t need to track the actual column<\/em> that it’s printing to. Instead, it can simply track how many spaces until the next tab stop<\/em>, and count down<\/em> to the next tab stop. That’s why every time the program prints a character, it subtracts one from the col<\/code> variable.<\/p>\n\n\n\n
If the program finds the end of a line, or when the program reaches the next tab stop, it resets the col<\/code> counter to the tab size, ready to count down to the next<\/em> tab stop.<\/p>\n\n\n\n
Putting it all together<\/h2>\n\n\n\n
Let’s put everything together into one source file, so we can compile our own program that expands tabs to spaces. Save this as untab.c<\/code> on your system:<\/p>\n\n\n\n
#include <stdio.h>\n\n#define TABSIZE 8\n\nint main()\n{\n    short col = TABSIZE;\n    int c;\n\n    while ((c = getchar()) != EOF) {\n        if (c == '\\t') {\n            while (col > 0) {\n                putchar(' ');\n                col--;\n            }\n        }\n        else {\n            putchar(c);\n            col--;\n        }\n\n        if ((c == '\\n') || (col == 0)) {\n            col = TABSIZE;\n        }\n    }\n\n    return 0;\n}<\/code><\/pre>\n\n\n\n
Compile it using your favorite C compiler, such as GCC on Linux. This is a very simple program, so you don’t need a special compiler or library to make it work:<\/p>\n\n\n\n
$ gcc -o untab untab.c<\/code><\/pre>\n\n\n\n
Now we need to test the program. It’s difficult to show a test file that has tabs in it<\/em> in an article like this, so let’s work around that limitation by writing a file that uses a different character that we can turn into a tab later using the tr<\/strong> command. In this case, let’s use #<\/code> as a “tab” placeholder:<\/p>\n\n\n\n
123456789012345678901234567890\n#|tab#|tab#|tab\n,,,,,,,,|space,,|space,,|space\na#|tab##|tab\nb,,,,,,,|space,,,,,,,,,,|space\na##|tab#|tab\nb,,,,,,,,,,,,,,,|space,,|space<\/code><\/pre>\n\n\n\n
Save this file as tab.txt<\/code>. I’ve started the test file with a list of numbers so you can see the first 30 columns. For each line with a tab, I’ve also written another line that has the correct number of extra spaces (typed as commas) to reach the next tab stop.<\/p>\n\n\n\n
If you convert the #<\/code> placeholders to tabs, then run the output through the new untab<\/strong> program, everything should line up:<\/p>\n\n\n\n
$ tr '#' '\\t' < tab.txt | .\/untab\n123456789012345678901234567890\n        |tab    |tab    |tab\n,,,,,,,,|space,,|space,,|space\na       |tab            |tab\nb,,,,,,,|space,,,,,,,,,,|space\na               |tab    |tab\nb,,,,,,,,,,,,,,,|space,,|space<\/code><\/pre>\n\n\n\n
We can verify that this is the correct behavior by replacing the untab<\/strong> program with the standard expand<\/strong> program:<\/p>\n\n\n\n
$ tr '#' '\\t' < tab.txt | expand\n123456789012345678901234567890\n        |tab    |tab    |tab\n,,,,,,,,|space,,|space,,|space\na       |tab            |tab\nb,,,,,,,|space,,,,,,,,,,|space\na               |tab    |tab\nb,,,,,,,,,,,,,,,|space,,|space<\/code><\/pre>\n\n\n\n
Make it your own<\/h2>\n\n\n\n
A program like this one is a great starting point if you want to learn about programming. There’s not much going on here; the program only needs to keep track of a few values, and is quite short, but it performs a very useful function to translate text files.<\/p>\n\n\n\n
If you want to learn about programming, try adapting this program to add other features. For example, you could replace TABSIZE<\/code> with a variable, and use a command line value to set the tab size. That makes the program more useful, especially if you prefer to have tabs displayed as four spaces instead of eight spaces. Feel free to make this program your own.<\/p>\n","protected":false},"excerpt":{"rendered":"
Learn how to write your own version of the ‘expand’ program, to convert tabs to spaces<\/p>\n","protected":false},"author":33,"featured_media":3096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[5,150],"tags":[91,152],"class_list":["post-14142","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","category-programming","tag-linux","tag-programming"],"modified_by":"Jim Hall","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/14142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=14142"}],"version-history":[{"count":2,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/14142\/revisions"}],"predecessor-version":[{"id":14144,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/14142\/revisions\/14144"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/3096"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=14142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=14142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=14142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}