gnome-builder issueshttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues2024-03-07T00:26:06Zhttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2170Ellipsized runtime name in comborow in the project's configuration makes it i...2024-03-07T00:26:06ZJeff FortinEllipsized runtime name in comborow in the project's configuration makes it impossible to know what runtime I'm onHi there!
This label here is ellipsized, and combined with the fact that the related popover menu widget does not show a visual indicaiton of what is actually selected, makes it impossible for me to know / confirm that I am on the maste...Hi there!
This label here is ellipsized, and combined with the fact that the related popover menu widget does not show a visual indicaiton of what is actually selected, makes it impossible for me to know / confirm that I am on the master/nightly version of the SDK for any given project's configuration:
![Screenshot_from_2024-03-06_19-16-27](/uploads/ae7ffdc950312d9b18c5ff0085d4b6a8/Screenshot_from_2024-03-06_19-16-27.png)
I've been meaning to report this for a while; I'm currently running version 45.0, but I think I've experienced this problem on every version before.
My font scaling setting is set to 1.00, so it's presumably not "Large Text" accessibility causing this.https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2078Builder kills all terminal windows on exit if the first one was open from Bui...2023-07-19T01:40:51ZtwoBuilder kills all terminal windows on exit if the first one was open from Builder# Affected version
## Builder
- Nightly flatpak: Yes
- Other: flathub 43
## Console
- kgx 43.0-2 (debian/testing)
# Steps to reproduce
1. close all Console windows
2. open a project in Builder
3. right click a file in the project tree, ...# Affected version
## Builder
- Nightly flatpak: Yes
- Other: flathub 43
## Console
- kgx 43.0-2 (debian/testing)
# Steps to reproduce
1. close all Console windows
2. open a project in Builder
3. right click a file in the project tree, select open folder, with terminal
4. open another Console window
5. close all Builder windows
# Current behavior
all terminals are closed, including the ones opened outisde of Builderhttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2027Notification textDocument/didClose is not emitted2023-04-20T20:31:29ZJCWasmx86jcwasmx86@t-online.deNotification textDocument/didClose is not emitted# Affected version
- Nightly flatpak: Yes
# Steps to reproduce
1. Start with `flatpak run --env=JSONRPC_DEBUG=1 org.gnome.Builder.Devel -v`
2. Open a document of a type backed by a language server (Vala, Swift) (You should see that a `t...# Affected version
- Nightly flatpak: Yes
# Steps to reproduce
1. Start with `flatpak run --env=JSONRPC_DEBUG=1 org.gnome.Builder.Devel -v`
2. Open a document of a type backed by a language server (Vala, Swift) (You should see that a `textDocument/didOpen` notification is sent)
3. Close the document (No `textDocument/didClose` notification is sent)
# Current behavior
No `textDocument/didClose` is sent.
# Expected behavior
`textDocument/didClose` should be sent.
This notification is supported, as this code exists: https://gitlab.gnome.org/GNOME/gnome-builder/-/blob/main/src/libide/lsp/ide-lsp-client.c#L636
The function is called if the `buffer-unloaded` signal is emitted. This probably means that the buffer isn't getting unloaded.
# Additional information
```
[runtime.version]
version = "45.alpha"
channel = "flatpak-nightly"
identifier = "44.1-27-g23bb4ef2b"
```
It seems like the buffer is disposed before the buffer-unloaded signal is emitted:
(With a bit of instrumentation of mine)
```
07:57:14.0352 ide-buffer[ 12]: CRITICAL: Disposing buffer 0x55555acca3b0
07:57:14.0356 ide-buffer-manager[ 12]: CRITICAL: ide_buffer_manager_remove: 0x55555acca3b0
07:57:14.0356 ide-lsp-client[ 12]: CRITICAL: ide_lsp_client_supports_buffer: (nil) (text/plain)
07:57:14.0356 ide-lsp-client[ 12]: CRITICAL: ide_lsp_client_supports_buffer: (nil) (text/plain)
```
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2020Undo/redo destroys code2023-06-26T21:09:39ZSophie HeroldUndo/redo destroys codeI recently had multiple occurrences where using undo/redo destroyed my code by only doing the operations partially or wrong, not sure what exactly.
I think it happened in 44.2 and nightlyI recently had multiple occurrences where using undo/redo destroyed my code by only doing the operations partially or wrong, not sure what exactly.
I think it happened in 44.2 and nightlyhttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2019gtk_css_node_invalidate_timestamp()/libxml segfault when opening files2023-10-05T14:02:26ZJoshua Leegtk_css_node_invalidate_timestamp()/libxml segfault when opening files```
[runtime.version]
version = "45.alpha"
channel = "flatpak-nightly"
identifier = "44.1-12-g4673dae4a"
```
I've been getting a reoccurring crash when using Builder 43 that I noticed again after upgrading to 44. It tends to occur after ...```
[runtime.version]
version = "45.alpha"
channel = "flatpak-nightly"
identifier = "44.1-12-g4673dae4a"
```
I've been getting a reoccurring crash when using Builder 43 that I noticed again after upgrading to 44. It tends to occur after opening a source file while it's being indexed (applying highlighting, etc.) and can happen repeatedly when relaunching Builder with the same file open. I haven't notice it crashing on the same file reliably, just that when it does occur it can get tripped up on the same file multiple times until decides not to.
I thought it was about time to see if I could aid in tracking it down. While running 44 through GDB the backtrace led somewhere in libxml, but I haven't been able to reproduce that with nightly so far so I'm unsure if they're one in the same. This is what I'm getting from a similar crash in nightly:
```
Thread 1 "gnome-builder" received signal SIGSEGV, Segmentation fault.
0x00007ffff76bd110 in undefined_value () from /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
(gdb) bt full
#0 0x00007ffff76bd110 in undefined_value () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#1 0x00007ffff72f42cb in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#2 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#3 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#4 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#5 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#6 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#7 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#8 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#9 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#10 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#11 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#12 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#13 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#14 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#15 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#16 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#17 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#18 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#19 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#20 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#21 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#22 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#23 0x00007ffff72f42e0 in gtk_css_node_invalidate_timestamp () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#24 0x00007ffff72f4332 in gtk_css_node_invalidate_frame_clock () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#25 0x00007ffff731090d in gtk_css_widget_node_queue_callback () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#26 0x00007ffff729e495 in gtk_widget_on_frame_clock_update () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#27 0x00007ffff7b92442 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x00007ffff7ba65c8 in signal_emit_unlocked_R.isra.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#29 0x00007ffff7bad575 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#30 0x00007ffff7bad743 in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#31 0x00007ffff744414d in _gdk_frame_clock_emit_update () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#32 0x00007ffff7444e12 in gdk_frame_clock_paint_idle () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#33 0x00007ffff7444fa4 in gdk_frame_clock_flush_idle () at /usr/lib/x86_64-linux-gnu/libgtk-4.so.1
#34 0x00007ffff7a8da4f in g_timeout_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007ffff7a8cd49 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007ffff7a8d2a8 in g_main_context_iterate.constprop () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007ffff7a8d343 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007ffff7cd138d in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#39 0x0000555555634c6a in ()
#40 0x00007ffff202954a in __libc_start_call_main () at /usr/lib/x86_64-linux-gnu/libc.so.6
#41 0x00007ffff202960b in __libc_start_main () at /usr/lib/x86_64-linux-gnu/libc.so.6
#42 0x00005555556359b5 in _start ()
```
The backtrace from 44:
```
Thread 1 "gnome-builder" received signal SIGSEGV, Segmentation fault.
tcmalloc::SLL_PopRange (end=<synthetic pointer>, start=<synthetic pointer>, N=32, head=0x555555b55160) at src/linked_list.h:88
88 tmp = SLL_Next(tmp);
(gdb) bt full
#0 tcmalloc::SLL_PopRange(void**, int, void**, void**) (end=<synthetic pointer>, start=<synthetic pointer>, N=32, head=0x555555b55160) at src/linked_list.h:88
i = 12
tmp = 0x0
delta_bytes = 4096
batch_size = 32
tail = <optimized out>
head = <optimized out>
#1 tcmalloc::SLL_PopRange(void**, int, void**, void**) (end=<synthetic pointer>, start=<synthetic pointer>, N=32, head=0x555555b55160) at src/linked_list.h:79
delta_bytes = 4096
batch_size = 32
tail = <optimized out>
head = <optimized out>
#2 tcmalloc::ThreadCache::FreeList::PopRange(int, void**, void**) (end=<synthetic pointer>, start=<synthetic pointer>, N=32, this=0x555555b55160) at src/thread_cache.h:238
delta_bytes = 4096
batch_size = 32
tail = <optimized out>
head = <optimized out>
#3 tcmalloc::ThreadCache::ReleaseToCentralCache(tcmalloc::ThreadCache::FreeList*, unsigned int, int) (this=this@entry=0x555555b55040, src=src@entry=0x555555b55160, cl=<optimized out>, N=N@entry=32)
at src/thread_cache.cc:206
delta_bytes = 4096
batch_size = 32
tail = <optimized out>
head = <optimized out>
#4 0x00007ffff7de99a9 in tcmalloc::ThreadCache::ListTooLong(tcmalloc::ThreadCache::FreeList*, unsigned int) (this=0x555555b55040, list=0x555555b55160, cl=<optimized out>) at src/thread_cache.cc:164
batch_size = 32
#5 0x00007ffff6cc2f21 in xmlFreeNodeList () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#6 0x00007ffff6cc310c in xmlFreeProp () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#7 0x00007ffff6cc85ce in xmlUnsetProp () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#8 0x00007ffff6d5ee78 in xmlRelaxNGCleanupTree () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#9 0x00007ffff6d64b2a in xmlRelaxNGParse () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#10 0x00007ffff6d50dd0 in xmlTextReaderRelaxNGValidateInternal.constprop.0 () at /usr/lib/x86_64-linux-gnu/libxml2.so.2
#11 0x00007ffff6f995ba in file_parse () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#12 0x00007ffff6f9b9b5 in _gtk_source_language_file_parse_version2 () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#13 0x00007ffff6f53f6b in gtk_source_language_parse_file () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#14 0x00007ffff6f55033 in _gtk_source_language_create_engine () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#15 0x00007ffff6f3ca18 in gtk_source_buffer_set_language () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#16 0x000055555562b521 in ide_buffer_guess_language (self=0x55555aff9d30) at ../src/libide/code/ide-buffer.c:4012
manager = 0x5555566fd200
lang = 0x555559aba700
basename = 0x55555af01b40 "tct-exporter.h"
content_type = 0x555559a5e360 "text/x-chdr"
line = 0x55555ad2a880 "/*"
lang_id = 0x5555563a9e88 "chdr"
path = <optimized out>
file = <optimized out>
uncertain = 0
#17 0x00007ffff7b92442 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007ffff7ba6813 in signal_emit_unlocked_R.isra.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007ffff7bad6a5 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007ffff7bad873 in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007ffff6f8704b in validate_and_insert.part () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#22 0x00007ffff6f87663 in gtk_source_buffer_output_stream_write () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#23 0x00007ffff7c7e8b6 in g_output_stream_write () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#24 0x00007ffff6f49291 in read_cb () at /usr/lib/x86_64-linux-gnu/libgtksourceview-5.so.0
#25 0x00007ffff7c69a77 in async_ready_callback_wrapper () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#26 0x00007ffff7ca01cb in g_task_return_now () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#27 0x00007ffff7ca0205 in complete_in_idle_cb () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#28 0x00007ffff7a8cd99 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007ffff7a8d2f8 in g_main_context_iterate.constprop () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007ffff7a8d393 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007ffff7cd172d in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#32 0x0000555555621d2b in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:298
messages_debug = 0x0
app = 0x55555637e9c0
desktop = <optimized out>
standalone = 0
version = 0
ret = <optimized out>
```https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2018global search broken on unicode2023-08-27T14:41:29Ztwoglobal search broken on unicode# Affected version
- Nightly flatpak: didn't test because the flathub version is very recent. please tell if it needs to be reproduced in the build from the `gnome-nightly` flatpak repo
- Other: flathub 44.2
# Steps to reproduce
1. Open...# Affected version
- Nightly flatpak: didn't test because the flathub version is very recent. please tell if it needs to be reproduced in the build from the `gnome-nightly` flatpak repo
- Other: flathub 44.2
# Steps to reproduce
1. Open a project
2. Ctrl+Enter
3. Type anything
# Current behavior
- Cyrillic letters don't find anything, find irrelevant actions, find only a few actions, or for some single letter queries, show two results consisting of the number of the code point substracted by 'а' or 'А'
- Latin letters don't find any actions
# Expected behavior
search works
# Additional information
- `LANG=uk_UA.UTF-8`
<!-- Ignore the text under this line. -->Backloghttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2014Quick Highlight highlights search results2023-04-27T18:27:38ZRocketRideQuick Highlight highlights search results<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see http...<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/setup )
2. Copy and run the following command in a Terminal:
flatpak install --user --from https://nightly.gnome.org/repo/appstream/org.gnome.Builder.flatpakref
3) The Nightly version can now be launched from Activities, or with this command: flatpak run org.gnome.Builder.Devel
-->
# Affected version
- Nightly flatpak: Yes
- Other: Ubuntu devel, Builder 44.0-4-g5ee406eba
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Select some sequence without newline symbols
2. Press `<Ctrl>`+`<F>`
3. Press Move to previous/next match two times
# Current behavior
<!-- Describe the current behavior. -->
Quick Highlight highlights search results
# Expected behavior
<!-- Describe the expected behavior. -->
Quick Highlight doesn't highlight search results.
# Additional information
Reproduction of this bug with tweaked color scheme.\
![Kooha-2023-03-20-03-13-32](/uploads/dc529db84f222b0d10328060fbc0c7ff/Kooha-2023-03-20-03-13-32.mp4)
<!-- Ignore the text under this line. -->Backloghttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1958Auto-completion isn't rendered properly when switching between files2023-01-11T23:43:01ZWilliam Roywroy@proton.meAuto-completion isn't rendered properly when switching between filesAs discussed on matrix, switching from one file to another sometimes makes the auto-completion invisible:
(0:24)
![Screencast_from_2023-01-11_18-02-56](/uploads/b77ff49b556826c4f5dfb338a13796d4/Screencast_from_2023-01-11_18-02-56.webm...As discussed on matrix, switching from one file to another sometimes makes the auto-completion invisible:
(0:24)
![Screencast_from_2023-01-11_18-02-56](/uploads/b77ff49b556826c4f5dfb338a13796d4/Screencast_from_2023-01-11_18-02-56.webm)
```
[runtime.version]
version = "44.beta"
channel = "flatpak-nightly"
identifier = "44.alpha-1-ge8333c2de"
[runtime.libraries]
glib = "2.75.2"
gtk = "4.9.3"
libadwaita = "1.3.0"
[build.libraries]
glib = "2.75.1"
gtk = "4.9.3"
libadwaita = "1.3.0"
[runtime.display]
name = "wayland-0"
n_monitors = 1
geometry[0] = [3840,2160]
```https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1940Append a new empty line to any opened file2023-03-15T04:22:00ZCédric BellegardeAppend a new empty line to any opened file# Affected version
- Nightly flatpak: Yes
- Other: Flathub 43 version
# Steps to reproduce
1. Open a file (any source type)
2. Builder appends a new empty line at the end
3. Modify file content
4. Save & close file
5. Reopen file
6. Bui...# Affected version
- Nightly flatpak: Yes
- Other: Flathub 43 version
# Steps to reproduce
1. Open a file (any source type)
2. Builder appends a new empty line at the end
3. Modify file content
4. Save & close file
5. Reopen file
6. Builder appends a new empty line at the end (two new empty line)
7. Loop from 3 to 6
# Current behavior
Source file contains as many empty lines than how many times you saved/close/open your file
# Expected behavior
Only one empty line or even better, no empty line at all.
# Additional information
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1928single quote/apostrophe is doubled inside strings2023-04-01T19:46:39Ztwosingle quote/apostrophe is doubled inside strings# Affected version
- flatpak stable
# Steps to reproduce
press ' inside a double-quoted string
# Current behavior
<!-- Describe the current behavior. -->
`'` is inserted both before and after the cursor, e.g. `"Файли об'єднано'"` (it's ...# Affected version
- flatpak stable
# Steps to reproduce
press ' inside a double-quoted string
# Current behavior
<!-- Describe the current behavior. -->
`'` is inserted both before and after the cursor, e.g. `"Файли об'єднано'"` (it's the last char here)
# Expected behavior
<!-- Describe the expected behavior. -->
only one `'` is inserted, e.g. `"Файли об'єднано"`
# Additional information
- Wayland
- no .editorconfig is present and C language settings were not modified
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1872Deleted files re-appear2023-03-15T04:41:45ZSophie HeroldDeleted files re-appearNightly
So I don't have an exact reproducer at all for this. I think @haecker-felix talked about this issue first, and I didn't want to believe it.
But it also happens to me: I have autosave disabled, and the file is not open in a tab....Nightly
So I don't have an exact reproducer at all for this. I think @haecker-felix talked about this issue first, and I didn't want to believe it.
But it also happens to me: I have autosave disabled, and the file is not open in a tab. I have deleted the file via Builder and Builder's terminal. And the file randomly (?) keeps re-appears on the disk.https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1825New line after comment unexpected behavior2022-10-06T16:29:10ZCorey BerlaNew line after comment unexpected behavior<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see http...<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/setup )
2. Copy and run the following command in a Terminal:
flatpak install --user --from https://nightly.gnome.org/repo/appstream/org.gnome.Builder.flatpakref
3) The Nightly version can now be launched from Activities, or with this command: flatpak run org.gnome.Builder.Devel
-->
# Affected version
- Nightly flatpak: Yes
- Other: 43.0
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Put your cursor at the end of a comment within a function
2. Hit enter
3.
# Current behavior
<!-- Describe the current behavior. -->
Cursor jumps up and text is moved around in an unexpected way
# Expected behavior
<!-- Describe the expected behavior. -->
# Additional information
<!--
Provide more information that could be relevant.
If the issue is a crash, provide a stack trace following the steps in:
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
-->
![Screencast_from_09-27-2022_02_00_03_PM](/uploads/a6de5b18d1d28bcdb04be1083aba9a8c/Screencast_from_09-27-2022_02_00_03_PM.webm)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/112Files are autosaved, messing up when git rebasing2022-10-05T20:48:28ZBugzillaFiles are autosaved, messing up when git rebasing## Submitted by Carlos Soriano Admin Account `@csoriano-admin-account`
**[Link to original bug (#764592)](https://bugzilla.gnome.org/show_bug.cgi?id=764592)**
## Description
I'm not sure, but seems files are autosaved in some circum...## Submitted by Carlos Soriano Admin Account `@csoriano-admin-account`
**[Link to original bug (#764592)](https://bugzilla.gnome.org/show_bug.cgi?id=764592)**
## Description
I'm not sure, but seems files are autosaved in some circumstances?
This is a problem when git rebasing, the files seems to be autosaved with the old content when not even having gnome-builder focused, messing up the rebase.
In case there is autosave, I wonder how useful is it, at least if done directly in the original file instead of in a cache.