{"id":3706,"date":"2024-01-22T02:16:00","date_gmt":"2024-01-22T07:16:00","guid":{"rendered":"https:\/\/www.both.org\/?p=3706"},"modified":"2024-01-22T06:35:55","modified_gmt":"2024-01-22T11:35:55","slug":"supercharge-libreoffice-with-command-line-automation","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=3706","title":{"rendered":"Supercharge LibreOffice with Command Line Automation"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n <\/span>\r\n<\/div><\/div>\n

LibreOffice has all the productivity features you’d want from an office software suite, making it a popular open source alternative to Microsoft Office or Google Suite. One of LibreOffice’s powers is the ability to operate from the command line. For example, Seth Kenlon recently explained how he uses a global command-line option to convert multiple files<\/a> from DOCX to EPUB with LibreOffice. His article inspired me to share some other LibreOffice command-line tips and tricks.<\/p>\n\n\n\n

Before we look at some hidden features of LibreOffice commands, you need to understand how to use options with applications. Not all applications accept options (aside from the basics like the --help<\/code> option, which works in most Linux applications).<\/p>\n\n\n\n

$ libreoffice --help<\/code><\/pre>\n\n\n\n
This returns descriptions of other options LibreOffice accepts. Some applications don’t have many options, but LibreOffice has a few screens worth, so there’s plenty to play with.<\/p>\n\n\n\n
Here are five useful things you can do with LibreOffice at the terminal to make the software even more useful.<\/p>\n\n\n\n
1. Customize your launch options<\/h2>\n\n\n\n
You can modify how you launch LibreOffice. For instance, if you want to open just LibreOffice’s word processor component:<\/p>\n\n\n\n
$ libreoffice --writer  #starts the word processor<\/code><\/pre>\n\n\n\n
You can open its other components similarly:<\/p>\n\n\n\n
$ libreoffice --calc  #starts the Calc document\n$ libreoffice --draw  #starts an empty Draw document\n$ libreoffice --web  #starts and empty HTML document<\/code><\/pre>\n\n\n\n
You also can access specific help files from the command line:<\/p>\n\n\n\n
$ libreoffice --helpwriter<\/code><\/pre>\n\n\n\n
\"LibreOffice<\/figure>\n\n\n\n
Or if you need help with the spreadsheet application:<\/p>\n\n\n\n
$ libreoffice --helpcalc<\/code><\/pre>\n\n\n\n
You can start LibreOffice without the splash screen:<\/p>\n\n\n\n
$ libreoffice --writer --nologo<\/code><\/pre>\n\n\n\n
You can even have it launch minimized in the background while you finish working in your current window:<\/p>\n\n\n\n
$ libreoffice --writer --minimized<\/code><\/pre>\n\n\n\n
2. Open a file in read-only mode<\/h2>\n\n\n\n
You can open files in read-only mode using --view<\/code> to prevent accidentally making and saving changes to an important file:<\/p>\n\n\n\n
$ libreoffice --view example.odt<\/code><\/pre>\n\n\n\n
3. Open a document as a template<\/h2>\n\n\n\n
Have you ever created a document to use as a letterhead or invoice form? LibreOffice has a rich built-in template system, but you can make any document a template with the -n<\/code> option:<\/p>\n\n\n\n
$ libreoffice --writer -n example.odt<\/code><\/pre>\n\n\n\n
Your document will open in LibreOffice and you can make changes to it, but you won’t overwrite the original file when you save it.<\/p>\n\n\n\n
4. Convert documents<\/h2>\n\n\n\n
When you need to do a small task like converting a file to a new format, it can take as long for the application to launch as it takes to do the task. The solution is the --headless<\/code> option, which executes LibreOffice processes without launching the graphical user interface.<\/p>\n\n\n\n
For example, converting a document to EPUB is a pretty simple task in LibreOffice\u2014but it’s even easier with the libreoffice<\/code> command:<\/p>\n\n\n\n
$ libreoffice --headless --convert-to epub example.odt<\/code><\/pre>\n\n\n\n
Using wildcards means you can convert dozens of documents at once:<\/p>\n\n\n\n
$ libreoffice --headless --convert-to epub *.odt<\/code><\/pre>\n\n\n\n
You can convert files to several formats, including PDF, HTML, DOC, DOCX, EPUB, plain text, and many more.<\/p>\n\n\n\n
5. Print from the terminal<\/h2>\n\n\n\n
You can print LibreOffice documents from the command line without opening the application:<\/p>\n\n\n\n
$ libreoffice --headless -p example.odt<\/code><\/pre>\n\n\n\n
This option prints to the default printer without opening LibreOffice; it just sends the document to your printer.<\/p>\n\n\n\n
To print all the files in a directory:<\/p>\n\n\n\n
$ libreoffice -p *.odt<\/code><\/pre>\n\n\n\n
(More than once, I’ve issued this command and then run out of paper, so make sure you have enough paper loaded in your printer before you start.)<\/p>\n\n\n\n
You can also print files to PDF. There’s usually no difference between this and using the --convert-to-pdf<\/code> option but it’s easy to remember:<\/p>\n\n\n\n
$ libreoffice --print-to-file example.odt --headless<\/code><\/pre>\n\n\n\n
Bonus: Flatpak and command options<\/h2>\n\n\n\n
If you installed LibreOffice as a Flatpak<\/a>, all of these command options work, but you have to pass them through Flatpak. Here’s an example:<\/p>\n\n\n\n
$ flatpak run org.libreoffice.LibreOffice --writer<\/code><\/pre>\n\n\n\n
It’s a lot more verbose than a local install, so you might be inspired to write a Bash alias<\/a> to make it easier to interact with LibreOffice directly.<\/p>\n\n\n\n
Surprising terminal options<\/h2>\n\n\n\n
Find out how you can extend the power of LibreOffice from the command line by consulting the man pages:<\/p>\n\n\n\n
$ man libreoffice<\/code><\/pre>\n\n\n\n
Were you aware that LibreOffice had such a rich set of command-line options? Have you discovered other options that nobody else seems to know about? Share them — send an email to Open@Botrh.org and we’ll collect them into a follow-up article.<\/p>\n","protected":false},"excerpt":{"rendered":"
Did you know that one of LibreOffice’s powers is the ability to operate from the command line like converting documents from one format to another?<\/p>\n","protected":false},"author":32,"featured_media":3715,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[100,237],"tags":[133],"class_list":["post-3706","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-command-line","category-libreoffice","tag-libreoffice"],"modified_by":"David Both","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/3706","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\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3706"}],"version-history":[{"count":3,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/3706\/revisions"}],"predecessor-version":[{"id":3712,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/3706\/revisions\/3712"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/3715"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3706"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3706"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}