DEV Community

Cover image for Pair programming with ChatGPT - an unexpected path
Nicola Massarenti
Nicola Massarenti

Posted on • Originally published at

Pair programming with ChatGPT - an unexpected path

ChatGPT is out there and everyone is talking about it. I have read tons of posts regarding how to write prompts, what prompt is going to give you the secret strategy for the business... yada yada yada...

My story, here, is not about prompt engineering.

It's about one unexpected outcome, about how, for the first time, I felt like I was getting help from a Senior peer: someone who understood my problem, someone located remotely (because I was chatting with him), someone that had more experience than me in Linux, someone I could learn from.

The problem

My OS is Linux Ubuntu. My shell is fish and I love it (check out my dotfiles). It allows the creation of functions (a.k.a. aliases) very easily.

My note-taking tool is Obsidian, an open source software for building the second brain (it's also where I'm drafting this blog post).

On Ubuntu, I run the Obsidian app by running an AppImage, a format for distributing software on Linux. An AppImage file contains the software and all the dependencies you need to run the app. This means that to run the file you only type one command: ./path/to/file.AppImage.

Well, running obsidian via AppImage implies the following steps:

  • Opening a terminal - typing: CTRL+T
  • Running the AppImage - typing: ./path/to/AppImage
  • Keeping the terminal open to keep the process up and running - the main problem, because I often do some house-cleaning and close all the pending processes and terminals

This means that I should repeat these three steps at least once a day. Every day.... This had to be automated!

What I wanted to do

My initial goal was to create a fish function that allowed me to type obsidian and, in turn, run the app image.

This creates the following function (located in ~/.config/fish/functions/

function obsidian --wraps=/opt/obsidian/Obsidian-1.1.9.AppImage --description 'alias obsidian=/opt/obsidian/Obsidian-1.0.3.AppImage'
  /opt/obsidian/Obsidian-1.0.3.AppImage $argv; 
Enter fullscreen mode Exit fullscreen mode

However, this partially solved my problem. I had to keep the terminal up and running. This is what the terminal was printing while Obsidian was running:

So I thought: I just have to redirect the logs to /dev/null and it's done! I can close or use the terminal for other stuff! Great!

At this point, I wanted a quick result since (I thought) I knew what was the path to follow. So, I decided to ask ChatGPT to solve the problem. I asked:
write a fish function that runs a detached appImage at path "/opt/obsidian/Obsidian-1.1.9.AppImage"

Great! I got the solution:

function run-obsidian
    nohup /opt/obsidian/Obsidian-1.1.9.AppImage > /dev/null 2>&1 &
Enter fullscreen mode Exit fullscreen mode

I modified the .fish file and tested the new function: obsidian was opened and the process was detached, but when I closed the terminal, obsidian was closed too!

Fair enough... With some disappointment, I wrote to ChatGPT: the process should be alive even if I kill the terminal.

And here happened the unexpected! Here I was suggested a new path, something I knew could be used for such use cases but for a lack of experience I never considered. Here I learned something new, without searching for it.

What I discovered it was possible

ChatGPT now shared an unexpected solution. It said that if I wanted to have the process running even if I logged out of the system, I had to use systemd service manager.

This is the service file generated:

# Create a new service file
sudo nano /etc/systemd/user/obsidian.service

# Add the following content to the file
Description=Obsidian AppImage



Enter fullscreen mode Exit fullscreen mode

And, I could use the following commands to enable and start the service:

systemctl --user enable obsidian.service
systemctl --user start obsidian.service
Enter fullscreen mode Exit fullscreen mode

This was my reaction:

I was stunned. This kind of interaction it's exactly what a person expects by a Senior colleague. I felt enriched from the answer. It was great.

Now, I had to automate the setup. I asked: create a script that automates the generation of the file, the setup of systemctl, and that runs the latest version of the AppImage among those in the folder. Make it fish-compliant

This was the output:

#!/usr/bin/env fish

# Edit this line to specify the path to your AppImages
set APPIMAGE_PATH '/opt/obsidian'

# Edit this line to specify the service name
set SERVICE_NAME 'obsidian'

# Find the latest AppImage
set appimage (find $APPIMAGE_PATH -name "Obsidian-*.AppImage" | sort -r | head -n 1)

# Create the service file
sudo sh -c "echo '[Unit]\nDescription=Obsidian AppImage\n\n[Service]\nExecStart=$appimage\nRestart=always\n\n[Install]\' > /etc/systemd/user/$SERVICE_NAME.service"

# Reload the systemd configuration
systemctl --user daemon-reload

# Enable the service
systemctl --user enable $SERVICE_NAME.service

# Start the service
systemctl --user start $SERVICE_NAME.service
Enter fullscreen mode Exit fullscreen mode

and it was done. Wow.

Top comments (0)