beamerpresenter.conf(5)
πΈ NAME πΈ
beamerpresenter.conf β configuration file for BeamerPresenter.
This is the beamerpresenter.conf(5) manual page β File Formats Manual, bestie β and it's here to make the config file make sense. π
π DESCRIPTION π
This man page explains the configuration file for BeamerPresenter, usually stored in $HOME/.config/beamerpresenter/beamerpresenter.conf (see FILES below). A different path can be specified on the command line using the option -c of the beamerpresenter command. You can manually edit this file or make changes in the settings widget of BeamerPresenter, which will also be written to this file. Command line arguments temporarily overwrite the settings of the configuration file.
The configuration is structured into groups. A group is started by a line of the format [name] where name is the name of the group. The group ends when another group is started. Entries not belonging to any group are put in the default group General.
It's giving very structured group-chat energy:[group]starts a thread, the next[group]ends it, and anything with no group lands inGeneral. π«Ά
π§ [General] π§
engine = mupdfβ PDF engine, bestie:"mupdf","poppler", or"qtpdf". This is only relevant when more than one PDF engine was enabled at compile time (command line option"--renderer"). πgui config = /etc/xdg/beamerpresenter/gui.jsonβ path to user interface configuration file (command line option"-g"or"--gui-config"). The structure of this file is documented inbeamerpresenter-ui(5). πmanual = /usr/share/doc/beamerpresenter/README.htmlβ path to HTML-formatted manual, which is shown in the settings widget. β¨icon path = /usr/share/beamerpresenter/iconsβ path to directory containing BeamerPresenter's own icons. Note that BeamerPresenter uses own icons and an icon theme installed on your system. π¦icon themeβ icon theme used for (generic) icons. Choose any icon theme installed on your system. πΈicon theme pathβ path to icon theme. If Qt does not find your icon theme, you can try to set its path with this option. π§cache pages = -1β maximum number of pages in cache. A negative number is interpreted as infinity. πmemory = 1.0486e+08β maximally allowed memory used to cache slides, floating point number in bytes. Note that this limit is not always strictly obeyed, since the required memory per page is unknown before rendering the page. πframe time = 50β frame time (integer, in ms) when showing slides in rapid succession as an animation. The actual frame time can be longer depending on the time needed to show the frame. βgestures = falseβ enable or disable gesture navigation (if available). In wayland and Xorg, 3 fingers swiping on a touch screen trigger a gesture event. Currently not configurable in the GUI. π«Άmax zoom increment = 0.2β maximum zoom increment when interpreting touch pinch gestures.0.25means that zoom increments must lie within the range-20% < increment < +25%. Value must be a positive number. This cutoff value helps avoiding wrong interpretation of pinch gestures with extreme zoom steps. πlog = falseβ log slide changes to standard output (command line option"--log"). π₯automatic slide changes = trueβ automatically switch slides if the PDF defines a duration for the slide. This can be used for very basic (and quite ugly) animations by showing slides in rapid succession. πexternal links = falseβ open external links using default programs (e.g. browser) and load remote resources (e.g. remote media linked from a presentation). If disabled, external links and remote media are ignored. πsearch highlight color = #6428643bβ color (#AARRGGBB) used to highlight search results. This should include transparency, because it is drawn on top of the search results. πdebug = flag1,flag2,...β only if debugging was enabled at compile time: show debugging messages for the given flags. Usually debugging flags are defined on the command line ("--debug") and not in the global configuration. π
π [drawing] π
history length hidden = 20β number of steps in drawing history (available undo steps) for slides, which are currently not visible. πhistory length visible = 50β number of steps in drawing history (available undo steps) for the currently active slide. β¨mode = cumulativeβ defines how drawings are associated to pages. Possible options are:per pageβ drawings are only connected to one page in the PDF file.per labelβ groups of successive pages which share the same page label have the same drawings. For presentations generated with LaTeX beamer this means that different overlays of the same slide show the same drawings. This mode can cause problems when combined with multimedia or slide transitions. πcumulativeβ drawings are connected to pages of the PDF file. But within a group of successive pages with the same page label the drawings of the previous page are copied to the next slide if this next slide does not contain any own drawings. This allows one to successively add drawings in slides, where items appear as overlays with the same page label. π
finalize drawn paths = falseβ if this is true, scaling a drawn path will only affect its coordinates, not the stroke itself. If this is false, lines will get thinner or thicker when rescaling the path. πsnap angle = 0.05β maximal slope for angle snapping to horizontal/vertical direction when detecting lines. βline sensitivity = 0.005β parameter defining sensitivity of shape detection for lines. Larger values will categorize more paths as lines. πΈellipse sensitivity = 0.05β parameter defining sensitivity of shape detection for ellipses. Larger values will categorize more paths as ellipses. π¦rectangle angle tolerance = 0.3β affects shape recognizer for rectangle: this defines the tolerance in angles of different sides of a rectangle (angle in radiant). π§rectangle closing tolerance =0.1β affects shape recognizer for rectangle: this defines the allowed distance between first and last point when drawing a rectangle relative to variance of point coordinates. πcircle threshold = 0.025β ellipses with a relative deviation of the two radii smaller than this number will be considered as circles. π₯arrow tip scale = 1.β size of the arrow tip relative to the default size. πarrow tip ratio = 1.2β length of the arrow tip relative to half of its width. π
π [selection] π
handle size = 7β size (in points) of the handles of the selection. β¨minimal path width = 3β minimal width (in points) of paths considered when selecting a path by clicking on it. A larger number makes it simpler to select thin lines by clicking on them. πselection color = #20808090β filling color of the selection rectangle. Make sure this is semi-transparent (in the form#aarrggbb). πΈselection outline color = #80808090β outline color of the selection rectangle. π¦selection outline width = 0.5β pen width for drawing the selection rectangle outline. π
π¦ [rendering] π¦
page part threshold = 2.5β threshold for the aspect ratio of PDF pages above which it is assumed that a PDF file contains slides and notes for the speaker side-by-side on the same PDF page. For slides generated with LaTeX beamer and the option"show notes on second screen"this allows one to show notes for the speak on one screen and presentation slides on a second screen. Note that this only has an effect if the configuration of the user interface (beamerpresenter-ui(5)) defines, which parts of the page should be shown on which screen. πrenderer = mupdfβ renderer that creates images from PDF pages. Allowed values are the ones defined at compile time. Usually only one renderer is enabled and this option is irrelevant. Possible values are"mupdf","poppler","qtpdf", and"external". An external renderer requires the configuration of rendering command and rendering arguments. Note that renderer and PDF engine must agree, i.e., it is not possible to use the Poppler engine and MuPDF for rendering. π₯max image size = 2e7β maximum number of pixels in an image. This should always be larger than the number of pixels of your screen. When zooming into a page, a larger image of the page will be rendered. This will be refused if the image becomes too large. Adjust this value to limit the maximum memory usage of BeamerPresenter. πrendering commandβ path to external program used to render pages. This only has an effect ifrendereris set toexternal. πrendering argumentsβ comma-separated list of arguments for external program used to render pages. This only has an effect ifrendereris set toexternaland external rendering was enabled at compile time. The following replacements in the arguments are available:%fileβ absolute path to PDF file%pageβ page number, start counting from 1%0pageβ page number, start counting from 0%resolutionβ resolution in dpi%width, %heightβ target image size in pixels%formatβ"png"or"pnm": image format.%Format.β"PNG"or"PNM": image format.
π [keys] π
All keyboard shortcut definitions are of the form
key code = handler.
Here key code is anything that Qt can interpret as a key code, e.g., "A", "Shift+B", or "Ctrl+Alt+Shift+C". For handler the following formats are allowed:
actionβ string representing an action. The available actions are listed inbeamerpresenter-ui(5). β¨action1, action2, ...β comma-separated list of actions. π- JSON dictionary β JSON-formatted dictionary defining a tool. Use single quotation marks instead of double quotation marks, or escape double quotation marks using backslash. Entries in the dictionary are:
toolβ mandatory:pen,fixed width pen,highlighter,eraser,pointer,magnifier,torch,text,click select,rectangle select,freehand select, ornone
deviceβ optional π« use the tool for the given devices and leave every other device exactly as it was. You can pass either one single device or a list (JSON array) of device names. The names you're allowed to use are:- left button (equivalent: mouse)
- right button
- middle button
- no button (only mouse cursor moves)
- touch
- tablet pen
- tablet (may include tablet input which is not recognized as pen)
- tablet eraser
- tablet hover (tablet event with zero pressure)
- tablet cursor
- tablet other
- tablet mod
- tablet all (any tablet input device)
- all (devices which are commonly used like left mouse button)
- all+ (devices except right mouse button, middle mouse button, tablet eraser)
- all++ (really all devices)
like, "really all" means REALLY all, bestie β no crumbs left π
colorβ a color name known to Qt, or#RRGGBB, or#AARRGGBBπ¨widthβ only draw tools (pen, highlighter, fixed width pen): stroke width (positive number).sizeβ only pointing tools (pointer, torch, eraser): radius of tool (positive number). it's giving "how chunky is my circle" energy β¨fillβ only draw tools (pen, highlighter, fixed width pen): color to fill the path. Leave it empty if paths should not be filled.style=solidβ only draw tools: Pen style for stroking the path. Possible values are"nopen","solid","dash","dot","dashdot", and"dashdotdot". (yes"nopen"is a real value, we don't make the rules π«Ά)brush=SolidPatternβ only draw tools: filling style of the path, see https://doc.qt.io/qt-6/qt.html#BrushStyle-enum for valid names. Gradients are not allowed β sorry to the gradient girlies πshape=freehandβ only draw tools: draw this shape instead of a freehand path. Allowed values are"freehand","rectangle","ellipse","line", and"arrow".scale=2β only magnifier: magnification factor (number between0.1and5).linewidth=0β only eraser: draw a circle of given line width around the eraser (number). The circle is only drawn on the currently active widget. main character eraser only πfontβ only text tool: anything that Qt can interpret as font name.font sizeβ only text tool: font size (positive number).
Examples: here's the vibe, copy-paste away bestie π
{'tool':'pen', 'color':'green', 'width':2,
'device':['tablet pen', 'touch']}
{'tool':'pointer', 'color':'#ffff0000', 'size':10,
'device':'all'}
π¦ JSON array
Literally just an array of JSON dictionaries as described before. The dictionaries should contain complementing values for device. they tag-team it, iykyk β¨
π [gestures]
Connect gestures to actions using the same syntax as for keyboard shortcuts in [keys]:
gesture = handler
Valid gestures are: swipe left, swipe right, swipe up, swipe down. Currently gesture settings cannot be changed in the graphical interface. (GUI said "not today", so it's config-file o'clock π«Ά)
π§ [tools]
Define tools which are initially associated with a devices. The syntax is as follows:
device = tool
Here device is a device name as listed above and tool is a JSON object representing a tool as described above. If tool defines a device (or list of devices), this overwrites device. It is therefore also possible to use any unique string or number for device and specify the device(s) in the tool JSON object. convenient? yes. chaotic? also yes π
An example configuration:
right button = {'tool':'eraser', 'size':10, 'linewidth':0.5}
tablet eraser = {'tool':'eraser', 'size':15, 'linewidth':0}
π FILES
/etc/xdg/beamerpresenter/beamerpresenter.confβ System-wide configuration file. This file is read before reading also the per-user configuration file.~/.config/beamerpresenter/beamerpresenter.confβ Per-user configuration file. Changes made through the graphical interface will be saved to this file. this is the one your GUI edits, so touch it gently π₯Ί
π SEE ALSO
beamerpresenter(1), beamerpresenter-ui(5)
okay that's the whole page bestie, you ATE that π go forth and configure β¨
this iconic lil' manual is from version 0.2.6, dated 2024-12-25 β happy reading and happy holidays, mwah ππ
π¦ where this page comes from
- nixos 26.05: beamerpresenter 0.2.6
- nixpkgs unstable: beamerpresenter 0.2.6
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms