NOTIFY-SEND(1)
๐ NAME ๐
ok so notify-send โ it's a program to send desktop notifications ๐ฆ like literally it pings your notification daemon from the command line, no big deal, just main character energy โจ
โจ SYNOPSIS โจ
notify-send [OPTIONS] {summary} [body]
๐ธ DESCRIPTION ๐ธ
bestie. with notify-send you can send desktop notifications to the user through a notification daemon, straight from the command line ๐
no GUI needed, no fuss, we love that for us.
these notifications are perfect for telling the user about an event, or just showing them some info, all without getting in their way. it's giving respectful. it's giving polite. it's giving iconic ๐
๐ OPTIONS ๐
-?,--helpโ shows the help and dips out, bye ๐จ-a,--app-name=APP_NAMEโ sets the app name for the notification, so everyone knows who's talking ๐ซถ-A,--action=[NAME=]Text...โ picks the actions to show the user. heads up, this one implies--wait, so it's gonna sit there and wait for the user to actually do something. you can set it multiple times if you're feeling extra ๐ theNAMEof the action gets output to stdout. and if you don't give aNAME? then the numerical index of the option is used instead, starting from1. slay.--selected-action-fd=FILE_DESCRIPTORโ the file descriptor where the action chosen by the user gets written ๐--activation-token-fd=FILE_DESCRIPTORโ the file descriptor where the action activation token gets written. note: the daemon has to support it, so it's a vibe check situation ๐ญ-u,--urgency=LEVELโ sets the urgency level. your options arelow,normal,critical๐ฅ-t,--expire-time=TIMEโ how long, in milliseconds, the notification stays on screen โฐ
real talk though: not every implementation actually uses this parameter ๐ฌ GNOME Shell and Notify OSD always ignore it, and Plasma ignores it for notifications with the critical urgency level. so likeโฆ set it, but don't be shocked.
-i,--icon=ICONโ sets an icon filename or a stock icon to display ๐-n,--app-icon=ICONโ sets an application icon filename or app icon name. the server may or may not display it, so it's giving maybe ๐-c,--category=TYPE[,TYPE...]โ sets the notification category ๐ท๏ธ-h,--hint=TYPE:NAME:VALUEโ passes some basic extra data along. valid types areBOOLEAN,INT,DOUBLE,STRING,BYTEandVARIANT๐ซ-p,--print-idโ prints the notification ID ๐--id-fd=FILE_DESCRIPTORโ the file descriptor where the notification ID gets written โ๏ธ-r,--replace-id=REPLACE_IDโ the ID of the notification you want to replace โป๏ธ-w,--waitโ waits for the notification to be closed before exiting. and if the expire-time is set, that gets used as the maximum waiting time, so it won't wait forever bestie โณ-e,--transientโ shows a transient notification. transient notifications by-pass the server's persistence capability, if it even has one. which means it won't be preserved until the user acknowledges it. it's a one-shot, no saving it for later ๐
๐ฆ SEE ALSO ๐ฆ
the Desktop Notification Spec lives over at https://specifications.freedesktop.org/notification-spec/ โ go read it, iykyk ๐
๐ AUTHORS ๐
- Andre Filipe de Assuncao e Brito <decko@noisemakers.org> โ Original author ๐
- Paul van Tilburg <paulvt@debian.org> โ Original author ๐
- Riccardo Setti <giskard@debian.org> โ Original author ๐
ok that's the whole thing, you're basically a notification wizard now ๐งโโ๏ธโจ this page came from libnotify and it's the NOTIFY-SEND(1) manual, fr fr. go forth and notify, bestie ๐๐ธ๐
๐ฆ where this page comes from
- fedora 43: libnotify 0.8.8-1.fc43
- fedora 43: libnotify 0.8.8-1.fc43
- fedora 43: libnotify 0.8.9-1.fc43 ยท LGPL-2.1-or-later
- fedora 43: libnotify 0.8.9-1.fc43 ยท LGPL-2.1-or-later
- fedora 44: libnotify 0.8.8-1.fc44 ยท LGPL-2.1-or-later
- fedora 44: libnotify 0.8.8-1.fc44 ยท LGPL-2.1-or-later
- fedora 44: libnotify 0.8.9-1.fc44 ยท LGPL-2.1-or-later
- fedora 44: libnotify 0.8.9-1.fc44 ยท LGPL-2.1-or-later
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms