X-Git-Url: https://git.lttng.org/?a=blobdiff_plain;f=doc%2Fman%2Flttng-enable-event.1.txt;h=b58691ba018c900a331fe2e29b3f7ff0d67af3f4;hb=9c1fd404f5ed2b39e31078fd2fc4efdb75d32e73;hp=4d88bdb1b6d37480287c796d1ba92c97942f7db6;hpb=e9b06e2bf2e5b0e8627e0944cc2f087eebc52e98;p=lttng-tools.git

diff --git a/doc/man/lttng-enable-event.1.txt b/doc/man/lttng-enable-event.1.txt
index 4d88bdb1b..b58691ba0 100644
--- a/doc/man/lttng-enable-event.1.txt
+++ b/doc/man/lttng-enable-event.1.txt
@@ -106,6 +106,7 @@ a _don't care_.
 
 For example, consider the following commands:
 
+[role="term"]
 ----------------------------------------------------------------
 lttng enable-event --userspace hello:world
 lttng enable-event --userspace hello:world --loglevel=TRACE_INFO
@@ -180,6 +181,10 @@ when creating a new event rule. If the filter expression evaluates
 to true when executed against the dynamic values of an event's fields
 when tracing, the filtering condition passes.
 
+NOTE: Make sure to **single-quote** the filter expression when running
+the command from a shell, as filter expressions typically include
+characters having a special meaning for most shells.
+
 The filter expression syntax is very similar to C language conditional
 expressions (expressions that can be evaluated by an `if` statement).