Memory-managed wrapper type.

Type class for types which can be safely cast to TextBuffer, for instance with toTextBuffer.

Cast to TextBuffer, for types for which this is known to be safe. For general casts, use castTo.

A convenience alias for Nothing :: Maybe TextBuffer.

Adds the mark at position where. The mark must not be added to another buffer, and if its name is not Nothing then there must not be another mark in the buffer with the same name.

Emits the TextBuffer::mark-set signal as notification of the mark's initial placement.

Since: 2.12

Adds clipboard to the list of clipboards in which the selection contents of buffer are available. In most cases, clipboard will be the Clipboard of type GDK_SELECTION_PRIMARY for a view of buffer.

Emits the “apply-tag” signal on buffer. The default handler for the signal applies tag to the given range. start and end do not have to be in order.

Calls textTagTableLookup on the buffer’s tag table to get a TextTag, then calls textBufferApplyTag.

Performs the appropriate action as if the user hit the delete key with the cursor at the position specified by iter. In the normal case a single character will be deleted, but when combining accents are involved, more than one character can be deleted, and when precomposed character and accent combinations are involved, less than one character will be deleted.

Because the buffer is modified, all outstanding iterators become invalid after calling this function; however, the iter will be re-initialized to point to the location where text was deleted.

Since: 2.6

Called to indicate that the buffer operations between here and a call to textBufferEndUserAction are part of a single user-visible operation. The operations between textBufferBeginUserAction and textBufferEndUserAction can then be grouped when creating an undo stack. TextBuffer maintains a count of calls to textBufferBeginUserAction that have not been closed with a call to textBufferEndUserAction, and emits the “begin-user-action” and “end-user-action” signals only for the outermost pair of calls. This allows you to build user actions from other user actions.

The “interactive” buffer mutation functions, such as textBufferInsertInteractive, automatically call begin/end user action around the buffer operations they perform, so there's no need to add extra calls if you user action consists solely of a single call to one of those functions.

Copies the currently-selected text to a clipboard.

This is a convenience function which simply creates a child anchor with textChildAnchorNew and inserts it into the buffer with textBufferInsertChildAnchor. The new anchor is owned by the buffer; no reference count is returned to the caller of textBufferCreateChildAnchor.

Creates a mark at position where. If markName is Nothing, the mark is anonymous; otherwise, the mark can be retrieved by name using textBufferGetMark. If a mark has left gravity, and text is inserted at the mark’s current location, the mark will be moved to the left of the newly-inserted text. If the mark has right gravity (leftGravity = False), the mark will end up on the right of newly-inserted text. The standard left-to-right cursor is a mark with right gravity (when you type, the cursor stays on the right side of the text you’re typing).

The caller of this function does not own a reference to the returned TextMark, so you can ignore the return value if you like. Marks are owned by the buffer and go away when the buffer does.

Emits the TextBuffer::mark-set signal as notification of the mark's initial placement.

Copies the currently-selected text to a clipboard, then deletes said text if it’s editable.

Deletes text between start and end. The order of start and end is not actually relevant; textBufferDelete will reorder them. This function actually emits the “delete-range” signal, and the default handler of that signal deletes the text. Because the buffer is modified, all outstanding iterators become invalid after calling this function; however, the start and end will be re-initialized to point to the location where text was deleted.

Deletes all editable text in the given range. Calls textBufferDelete for each editable sub-range of [start,end). start and end are revalidated to point to the location of the last deleted range, or left untouched if no text was deleted.

Deletes mark, so that it’s no longer located anywhere in the buffer. Removes the reference the buffer holds to the mark, so if you haven’t called objectRef on the mark, it will be freed. Even if the mark isn’t freed, most operations on mark become invalid, until it gets added to a buffer again with textBufferAddMark. Use textMarkGetDeleted to find out if a mark has been removed from its buffer. The TextBuffer::mark-deleted signal will be emitted as notification after the mark is deleted.

Deletes the mark named name; the mark must exist. See textBufferDeleteMark for details.

Deletes the range between the “insert” and “selection_bound” marks, that is, the currently-selected text. If interactive is True, the editability of the selection will be considered (users can’t delete uneditable text).

This function deserializes rich text in format format and inserts it at iter.

formats to be used must be registered using textBufferRegisterDeserializeFormat or textBufferRegisterDeserializeTagset beforehand.

Since: 2.10

This functions returns the value set with textBufferDeserializeSetCanCreateTags

Since: 2.10

Use this function to allow a rich text deserialization function to create new tags in the receiving buffer. Note that using this function is almost always a bad idea, because the rich text functions you register should know how to map the rich text format they handler to your text buffers set of tags.

The ability of creating new (arbitrary!) tags in the receiving buffer is meant for special rich text formats like the internal one that is registered using textBufferRegisterDeserializeTagset, because that format is essentially a dump of the internal structure of the source buffer, including its tag names.

You should allow creation of tags only if you know what you are doing, e.g. if you defined a tagset name for your application suite’s text buffers and you know that it’s fine to receive new tags from these buffers, because you know that your application can handle the newly created tags.

Since: 2.10

Should be paired with a call to textBufferBeginUserAction. See that function for a full explanation.

Retrieves the first and last iterators in the buffer, i.e. the entire buffer lies within the range [start,end).

Gets the number of characters in the buffer; note that characters and bytes are not the same, you can’t e.g. expect the contents of the buffer in string form to be this many bytes long. The character count is cached, so this function is very fast.

This function returns the list of targets this text buffer can provide for copying and as DND source. The targets in the list are added with info values from the TextBufferTargetInfo enum, using targetListAddRichTextTargets and targetListAddTextTargets.

Since: 2.10

This function returns the rich text deserialize formats registered with buffer using textBufferRegisterDeserializeFormat or textBufferRegisterDeserializeTagset

Since: 2.10

Initializes iter with the “end iterator,” one past the last valid character in the text buffer. If dereferenced with textIterGetChar, the end iterator has a character value of 0. The entire buffer lies in the range from the first position in the buffer (call textBufferGetStartIter to get character position 0) to the end iterator.

Indicates whether the buffer has some text currently selected.

Since: 2.10

Returns the mark that represents the cursor (insertion point). Equivalent to calling textBufferGetMark to get the mark named “insert”, but very slightly more efficient, and involves less typing.

Obtains the location of anchor within buffer.

Initializes iter to the start of the given line. If lineNumber is greater than the number of lines in the buffer, the end iterator is returned.

Obtains an iterator pointing to byteIndex within the given line. byteIndex must be the start of a UTF-8 character. Note bytes, not characters; UTF-8 may encode one character as multiple bytes.

Before the 3.20 version, it was not allowed to pass an invalid location.

Since the 3.20 version, if lineNumber is greater than the number of lines in the buffer, the end iterator is returned. And if byteIndex is off the end of the line, the iterator at the end of the line is returned.

Obtains an iterator pointing to charOffset within the given line. Note characters, not bytes; UTF-8 may encode one character as multiple bytes.

Before the 3.20 version, it was not allowed to pass an invalid location.

Since the 3.20 version, if lineNumber is greater than the number of lines in the buffer, the end iterator is returned. And if charOffset is off the end of the line, the iterator at the end of the line is returned.

Initializes iter with the current position of mark.

Initializes iter to a position charOffset chars from the start of the entire buffer. If charOffset is -1 or greater than the number of characters in the buffer, iter is initialized to the end iterator, the iterator one past the last valid character in the buffer.

Obtains the number of lines in the buffer. This value is cached, so the function is very fast.

Returns the mark named name in buffer buffer, or Nothing if no such mark exists in the buffer.

Indicates whether the buffer has been modified since the last call to textBufferSetModified set the modification flag to False. Used for example to enable a “save” function in a text editor.

This function returns the list of targets this text buffer supports for pasting and as DND destination. The targets in the list are added with info values from the TextBufferTargetInfo enum, using targetListAddRichTextTargets and targetListAddTextTargets.

Since: 2.10

Returns the mark that represents the selection bound. Equivalent to calling textBufferGetMark to get the mark named “selection_bound”, but very slightly more efficient, and involves less typing.

The currently-selected text in buffer is the region between the “selection_bound” and “insert” marks. If “selection_bound” and “insert” are in the same place, then there is no current selection. textBufferGetSelectionBounds is another convenient function for handling the selection, if you just want to know whether there’s a selection and what its bounds are.

Returns True if some text is selected; places the bounds of the selection in start and end (if the selection has length 0, then start and end are filled in with the same value). start and end will be in ascending order. If start and end are NULL, then they are not filled in, but the return value still indicates whether text is selected.

This function returns the rich text serialize formats registered with buffer using textBufferRegisterSerializeFormat or textBufferRegisterSerializeTagset

Since: 2.10

Returns the text in the range [start,end). Excludes undisplayed text (text marked with tags that set the invisibility attribute) if includeHiddenChars is False. The returned string includes a 0xFFFC character whenever the buffer contains embedded images, so byte and character indexes into the returned string do correspond to byte and character indexes into the buffer. Contrast with textBufferGetText. Note that 0xFFFC can occur in normal text as well, so it is not a reliable indicator that a pixbuf or widget is in the buffer.

Initialized iter with the first position in the text buffer. This is the same as using textBufferGetIterAtOffset to get the iter at character offset 0.

Get the TextTagTable associated with this buffer.

Returns the text in the range [start,end). Excludes undisplayed text (text marked with tags that set the invisibility attribute) if includeHiddenChars is False. Does not include characters representing embedded images, so byte and character indexes into the returned string do not correspond to byte and character indexes into the buffer. Contrast with textBufferGetSlice.

Inserts len bytes of text at position iter. If len is -1, text must be nul-terminated and will be inserted in its entirety. Emits the “insert-text” signal; insertion actually occurs in the default handler for the signal. iter is invalidated when insertion occurs (because the buffer contents change), but the default signal handler revalidates it to point to the end of the inserted text.

Simply calls textBufferInsert, using the current cursor position as the insertion point.

Inserts a child widget anchor into the text buffer at iter. The anchor will be counted as one character in character counts, and when obtaining the buffer contents as a string, will be represented by the Unicode “object replacement character” 0xFFFC. Note that the “slice” variants for obtaining portions of the buffer as a string include this character for child anchors, but the “text” variants do not. E.g. see textBufferGetSlice and textBufferGetText. Consider textBufferCreateChildAnchor as a more convenient alternative to this function. The buffer will add a reference to the anchor, so you can unref it after insertion.

Like textBufferInsert, but the insertion will not occur if iter is at a non-editable location in the buffer. Usually you want to prevent insertions at ineditable locations if the insertion results from a user action (is interactive).

defaultEditable indicates the editability of text that doesn't have a tag affecting editability applied to it. Typically the result of textViewGetEditable is appropriate here.

Calls textBufferInsertInteractive at the cursor position.

defaultEditable indicates the editability of text that doesn't have a tag affecting editability applied to it. Typically the result of textViewGetEditable is appropriate here.

Inserts the text in markup at position iter. markup will be inserted in its entirety and must be nul-terminated and valid UTF-8. Emits the TextBuffer::insert-text signal, possibly multiple times; insertion actually occurs in the default handler for the signal. iter will point to the end of the inserted text on return.

Since: 3.16

Inserts an image into the text buffer at iter. The image will be counted as one character in character counts, and when obtaining the buffer contents as a string, will be represented by the Unicode “object replacement character” 0xFFFC. Note that the “slice” variants for obtaining portions of the buffer as a string include this character for pixbufs, but the “text” variants do not. e.g. see textBufferGetSlice and textBufferGetText.

Copies text, tags, and pixbufs between start and end (the order of start and end doesn’t matter) and inserts the copy at iter. Used instead of simply getting/inserting text because it preserves images and tags. If start and end are in a different buffer from buffer, the two buffers must share the same tag table.

Implemented via emissions of the insert_text and apply_tag signals, so expect those.

Same as textBufferInsertRange, but does nothing if the insertion point isn’t editable. The defaultEditable parameter indicates whether the text is editable at iter if no tags enclosing iter affect editability. Typically the result of textViewGetEditable is appropriate here.

Moves mark to the new location where. Emits the TextBuffer::mark-set signal as notification of the move.

Moves the mark named name (which must exist) to location where. See textBufferMoveMark for details.

Creates a new text buffer.

Pastes the contents of a clipboard. If overrideLocation is Nothing, the pasted text will be inserted at the cursor position, or the buffer selection will be replaced if the selection is non-empty.

Note: pasting is asynchronous, that is, we’ll ask for the paste data and return, and at some point later after the main loop runs, the paste data will be inserted.

This function moves the “insert” and “selection_bound” marks simultaneously. If you move them to the same place in two steps with textBufferMoveMark, you will temporarily select a region in between their old and new locations, which can be pretty inefficient since the temporarily-selected region will force stuff to be recalculated. This function moves them as a unit, which can be optimized.

This function registers a rich text deserialization function along with its mimeType with the passed buffer.

Since: 2.10

This function registers GTK+’s internal rich text serialization format with the passed buffer. See textBufferRegisterSerializeTagset for details.

Since: 2.10

This function registers a rich text serialization function along with its mimeType with the passed buffer.

Since: 2.10

This function registers GTK+’s internal rich text serialization format with the passed buffer. The internal format does not comply to any standard rich text format and only works between TextBuffer instances. It is capable of serializing all of a text buffer’s tags and embedded pixbufs.

This function is just a wrapper around textBufferRegisterSerializeFormat. The mime type used for registering is “application/x-gtk-text-buffer-rich-text”, or “application/x-gtk-text-buffer-rich-text;format=tagsetName” if a tagsetName was passed.

The tagsetName can be used to restrict the transfer of rich text to buffers with compatible sets of tags, in order to avoid unknown tags from being pasted. It is probably the common case to pass an identifier != Nothing here, since the Nothing tagset requires the receiving buffer to deal with with pasting of arbitrary tags.

Since: 2.10

Removes all tags in the range between start and end. Be careful with this function; it could remove tags added in code unrelated to the code you’re currently writing. That is, using this function is probably a bad idea if you have two or more unrelated code sections that add tags.

Removes a Clipboard added with textBufferAddSelectionClipboard.

Emits the “remove-tag” signal. The default handler for the signal removes all occurrences of tag from the given range. start and end don’t have to be in order.

Calls textTagTableLookup on the buffer’s tag table to get a TextTag, then calls textBufferRemoveTag.

This function moves the “insert” and “selection_bound” marks simultaneously. If you move them in two steps with textBufferMoveMark, you will temporarily select a region in between their old and new locations, which can be pretty inefficient since the temporarily-selected region will force stuff to be recalculated. This function moves them as a unit, which can be optimized.

Since: 2.4

This function serializes the portion of text between start and end in the rich text format represented by format.

formats to be used must be registered using textBufferRegisterSerializeFormat or textBufferRegisterSerializeTagset beforehand.

Since: 2.10

Used to keep track of whether the buffer has been modified since the last time it was saved. Whenever the buffer is saved to disk, call gtk_text_buffer_set_modified (buffer, FALSE). When the buffer is modified, it will automatically toggled on the modified bit again. When the modified bit flips, the buffer emits the TextBuffer::modified-changed signal.

Deletes current contents of buffer, and inserts text instead. If len is -1, text must be nul-terminated. text must be valid UTF-8.

This function unregisters a rich text format that was previously registered using textBufferRegisterDeserializeFormat or textBufferRegisterDeserializeTagset.

Since: 2.10

This function unregisters a rich text format that was previously registered using textBufferRegisterSerializeFormat or textBufferRegisterSerializeTagset

Since: 2.10

Get the value of the “copy-target-list” property. When overloading is enabled, this is equivalent to

get textBuffer #copyTargetList

Get the value of the “cursor-position” property. When overloading is enabled, this is equivalent to

get textBuffer #cursorPosition

Get the value of the “has-selection” property. When overloading is enabled, this is equivalent to

get textBuffer #hasSelection

Get the value of the “paste-target-list” property. When overloading is enabled, this is equivalent to

get textBuffer #pasteTargetList

Construct a GValueConstruct with valid value for the “tag-table” property. This is rarely needed directly, but it is used by new.

Get the value of the “tag-table” property. When overloading is enabled, this is equivalent to

get textBuffer #tagTable

Set the value of the “text” property to Nothing. When overloading is enabled, this is equivalent to

clear #text

Construct a GValueConstruct with valid value for the “text” property. This is rarely needed directly, but it is used by new.

Get the value of the “text” property. When overloading is enabled, this is equivalent to

get textBuffer #text

Set the value of the “text” property. When overloading is enabled, this is equivalent to

set textBuffer [ #text := value ]

Type for the callback on the (unwrapped) C side.

The ::apply-tag signal is emitted to apply a tag to a range of text in a TextBuffer. Applying actually occurs in the default handler.

Note that if your handler runs before the default handler it must not invalidate the start and end iters (or has to revalidate them).

See also: textBufferApplyTag, gtk_text_buffer_insert_with_tags(), textBufferInsertRange.

Connect a signal handler for the “apply-tag” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #applyTag callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferApplyTagCallback.

A convenience synonym for Nothing :: Maybe TextBufferApplyTagCallback.

Connect a signal handler for the “apply-tag” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #applyTag callback

Wrap a TextBufferApplyTagCallback into a C_TextBufferApplyTagCallback.

Type for the callback on the (unwrapped) C side.

The ::begin-user-action signal is emitted at the beginning of a single user-visible operation on a TextBuffer.

See also: textBufferBeginUserAction, textBufferInsertInteractive, textBufferInsertRangeInteractive, textBufferDeleteInteractive, textBufferBackspace, textBufferDeleteSelection.

Connect a signal handler for the “begin-user-action” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #beginUserAction callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferBeginUserActionCallback.

A convenience synonym for Nothing :: Maybe TextBufferBeginUserActionCallback.

Connect a signal handler for the “begin-user-action” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #beginUserAction callback

Wrap a TextBufferBeginUserActionCallback into a C_TextBufferBeginUserActionCallback.

Type for the callback on the (unwrapped) C side.

The ::changed signal is emitted when the content of a TextBuffer has changed.

Connect a signal handler for the “changed” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #changed callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferChangedCallback.

A convenience synonym for Nothing :: Maybe TextBufferChangedCallback.

Connect a signal handler for the “changed” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #changed callback

Wrap a TextBufferChangedCallback into a C_TextBufferChangedCallback.

Type for the callback on the (unwrapped) C side.

The ::delete-range signal is emitted to delete a range from a TextBuffer.

Note that if your handler runs before the default handler it must not invalidate the start and end iters (or has to revalidate them). The default signal handler revalidates the start and end iters to both point to the location where text was deleted. Handlers which run after the default handler (see g_signal_connect_after()) do not have access to the deleted text.

See also: textBufferDelete.

Connect a signal handler for the “delete-range” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #deleteRange callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferDeleteRangeCallback.

A convenience synonym for Nothing :: Maybe TextBufferDeleteRangeCallback.

Connect a signal handler for the “delete-range” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #deleteRange callback

Wrap a TextBufferDeleteRangeCallback into a C_TextBufferDeleteRangeCallback.

Type for the callback on the (unwrapped) C side.

The ::end-user-action signal is emitted at the end of a single user-visible operation on the TextBuffer.

See also: textBufferEndUserAction, textBufferInsertInteractive, textBufferInsertRangeInteractive, textBufferDeleteInteractive, textBufferBackspace, textBufferDeleteSelection, textBufferBackspace.

Connect a signal handler for the “end-user-action” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #endUserAction callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferEndUserActionCallback.

A convenience synonym for Nothing :: Maybe TextBufferEndUserActionCallback.

Connect a signal handler for the “end-user-action” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #endUserAction callback

Wrap a TextBufferEndUserActionCallback into a C_TextBufferEndUserActionCallback.

Type for the callback on the (unwrapped) C side.

The ::insert-child-anchor signal is emitted to insert a TextChildAnchor in a TextBuffer. Insertion actually occurs in the default handler.

Note that if your handler runs before the default handler it must not invalidate the location iter (or has to revalidate it). The default signal handler revalidates it to be placed after the inserted anchor.

See also: textBufferInsertChildAnchor.

Connect a signal handler for the “insert-child-anchor” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #insertChildAnchor callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferInsertChildAnchorCallback.

A convenience synonym for Nothing :: Maybe TextBufferInsertChildAnchorCallback.

Connect a signal handler for the “insert-child-anchor” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #insertChildAnchor callback

Wrap a TextBufferInsertChildAnchorCallback into a C_TextBufferInsertChildAnchorCallback.

Type for the callback on the (unwrapped) C side.

The ::insert-pixbuf signal is emitted to insert a Pixbuf in a TextBuffer. Insertion actually occurs in the default handler.

Note that if your handler runs before the default handler it must not invalidate the location iter (or has to revalidate it). The default signal handler revalidates it to be placed after the inserted pixbuf.

See also: textBufferInsertPixbuf.

Connect a signal handler for the “insert-pixbuf” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #insertPixbuf callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferInsertPixbufCallback.

A convenience synonym for Nothing :: Maybe TextBufferInsertPixbufCallback.

Connect a signal handler for the “insert-pixbuf” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #insertPixbuf callback

Wrap a TextBufferInsertPixbufCallback into a C_TextBufferInsertPixbufCallback.

Type for the callback on the (unwrapped) C side.

The ::insert-text signal is emitted to insert text in a TextBuffer. Insertion actually occurs in the default handler.

Note that if your handler runs before the default handler it must not invalidate the location iter (or has to revalidate it). The default signal handler revalidates it to point to the end of the inserted text.

See also: textBufferInsert, textBufferInsertRange.

Connect a signal handler for the “insert-text” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #insertText callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferInsertTextCallback.

A convenience synonym for Nothing :: Maybe TextBufferInsertTextCallback.

Connect a signal handler for the “insert-text” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #insertText callback

Wrap a TextBufferInsertTextCallback into a C_TextBufferInsertTextCallback.

Type for the callback on the (unwrapped) C side.

The ::mark-deleted signal is emitted as notification after a TextMark is deleted.

See also: textBufferDeleteMark.

Connect a signal handler for the “mark-deleted” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #markDeleted callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferMarkDeletedCallback.

A convenience synonym for Nothing :: Maybe TextBufferMarkDeletedCallback.

Connect a signal handler for the “mark-deleted” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #markDeleted callback

Wrap a TextBufferMarkDeletedCallback into a C_TextBufferMarkDeletedCallback.

Type for the callback on the (unwrapped) C side.

The ::mark-set signal is emitted as notification after a TextMark is set.

See also: textBufferCreateMark, textBufferMoveMark.

Connect a signal handler for the “mark-set” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #markSet callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferMarkSetCallback.

A convenience synonym for Nothing :: Maybe TextBufferMarkSetCallback.

Connect a signal handler for the “mark-set” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #markSet callback

Wrap a TextBufferMarkSetCallback into a C_TextBufferMarkSetCallback.

Type for the callback on the (unwrapped) C side.

The ::modified-changed signal is emitted when the modified bit of a TextBuffer flips.

See also: textBufferSetModified.

Connect a signal handler for the “modified-changed” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #modifiedChanged callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferModifiedChangedCallback.

A convenience synonym for Nothing :: Maybe TextBufferModifiedChangedCallback.

Connect a signal handler for the “modified-changed” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #modifiedChanged callback

Wrap a TextBufferModifiedChangedCallback into a C_TextBufferModifiedChangedCallback.

Type for the callback on the (unwrapped) C side.

The paste-done signal is emitted after paste operation has been completed. This is useful to properly scroll the view to the end of the pasted text. See textBufferPasteClipboard for more details.

Since: 2.16

Connect a signal handler for the “paste-done” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #pasteDone callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferPasteDoneCallback.

A convenience synonym for Nothing :: Maybe TextBufferPasteDoneCallback.

Connect a signal handler for the “paste-done” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #pasteDone callback

Wrap a TextBufferPasteDoneCallback into a C_TextBufferPasteDoneCallback.

Type for the callback on the (unwrapped) C side.

The ::remove-tag signal is emitted to remove all occurrences of tag from a range of text in a TextBuffer. Removal actually occurs in the default handler.

Note that if your handler runs before the default handler it must not invalidate the start and end iters (or has to revalidate them).

See also: textBufferRemoveTag.

Connect a signal handler for the “remove-tag” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after textBuffer #removeTag callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_TextBufferRemoveTagCallback.

A convenience synonym for Nothing :: Maybe TextBufferRemoveTagCallback.

Connect a signal handler for the “remove-tag” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on textBuffer #removeTag callback

Wrap a TextBufferRemoveTagCallback into a C_TextBufferRemoveTagCallback.