meld issueshttps://gitlab.gnome.org/GNOME/meld/-/issues2019-08-21T21:08:34Zhttps://gitlab.gnome.org/GNOME/meld/-/issues/362Allow spell checking in comments2019-08-21T21:08:34ZsilvioprogAllow spell checking in commentsHi.
It would be nice to allow spell checking in commit comments. Many tools allows it using `*.dic` files to check the words.
Thank you!Hi.
It would be nice to allow spell checking in commit comments. Many tools allows it using `*.dic` files to check the words.
Thank you!https://gitlab.gnome.org/GNOME/meld/-/issues/78[BZ#739184] Scrolling in central bar should scroll from screen position inste...2019-11-03T00:56:28ZBugzilla[BZ#739184] Scrolling in central bar should scroll from screen position instead of cursor## Submitted by Kai Willadsen
**[Link to original bug (#739184)](https://bugzilla.gnome.org/show_bug.cgi?id=739184)**
## Description
>>>
Currently, if you scroll with the mouse in the central bar on screen, Meld just runs the next-d...## Submitted by Kai Willadsen
**[Link to original bug (#739184)](https://bugzilla.gnome.org/show_bug.cgi?id=739184)**
## Description
>>>
Currently, if you scroll with the mouse in the central bar on screen, Meld just runs the next-diff/previous-diff action, which goes to the next/previous chunk *relative to the text cursor's position in the textview*. This often feel weird because you use the middle-bar scroll in different scenarios to the cursor-relative next/prev.
It would probably be nicer to pick the starting chunk (from which to choose what chunk is next/prev) as whatever chunk is closest to the middle of the screen. This can get slightly weird, since we end up guessing some of the time. However, if we combined this with a heuristic along the lines of "whatever chunk the cursor is in, if that chunk is near the middle of the screen, otherwise whatever chunk is actually in the middle of the screen" then we should be okay.
See discussion starting at:
https://mail.gnome.org/archives/meld-list/2014-September/msg00001.html
>>>https://gitlab.gnome.org/GNOME/meld/-/issues/168Can I tell which versions of a file actually differ in 3-way dir comparison?2019-11-17T03:36:59ZGhost UserCan I tell which versions of a file actually differ in 3-way dir comparison?**Short:**
In the 3-way directory comparison is there a way to tell whether all three versions of a file differ from each other or if two of them are the same and just one is different?
**Long:**
Thanks for Meld. It's great. I often use...**Short:**
In the 3-way directory comparison is there a way to tell whether all three versions of a file differ from each other or if two of them are the same and just one is different?
**Long:**
Thanks for Meld. It's great. I often use it before git merging/rebasing to evaluate changes and identify conflicts in advance. In that case I have:
* left - my local version
* middle - the base (common ancestor) version
* right - their remote version
Modified files are displayed blue and bold. The version with the latest change has a yellow star attached to it. But is there a way to tell, whether all the three versions of a file differ from each other (i.e. potential conflict) or if two of them are the same and just one differs from them? (I mean right away - in the directory comparison view without the need to open the file.)
If this feature is not available yet, would it be possible to add it? I hope it wouldn't be too difficult.
**Proposal:**
If two of the three versions of a file are identical and only one differs, they could all be blue (as they are now) but only the different version would be bold. The other two would have normal font-weight.
If all three versions differ from each other, display them all bold (as you do now). In this case I would even prefer if they could be displayed orange (or any other color) to emphasize the risk of a conflict. But that's not so important any more.
Thank you!!!https://gitlab.gnome.org/GNOME/meld/-/issues/72[BZ#727600] Add the command to push/pull just single or selected lines2019-11-19T23:16:50ZBugzilla[BZ#727600] Add the command to push/pull just single or selected lines## Submitted by xhp..@..com
**[Link to original bug (#727600)](https://bugzilla.gnome.org/show_bug.cgi?id=727600)**
## Description
>>>
When comparing files using Meld one can copy (delete, add) differing blocks between left and righ...## Submitted by xhp..@..com
**[Link to original bug (#727600)](https://bugzilla.gnome.org/show_bug.cgi?id=727600)**
## Description
>>>
When comparing files using Meld one can copy (delete, add) differing blocks between left and right panels easily however I'm lacking possibility to do the same just with a part of this block or single line in minimum.
Can this feature be added into meld?
So far the only option is to copy the text using clipboard or I'm missing something?
thanks
Jan
>>>https://gitlab.gnome.org/GNOME/meld/-/issues/93[BZ#755950] Feature: Column/Block Mode Editing2020-01-22T22:03:33ZBugzilla[BZ#755950] Feature: Column/Block Mode Editing## Submitted by sog..@..com
**[Link to original bug (#755950)](https://bugzilla.gnome.org/show_bug.cgi?id=755950)**
## Description
>>>
I was unable to find this feature in Meld, so I am making a request for it. I would not go into d...## Submitted by sog..@..com
**[Link to original bug (#755950)](https://bugzilla.gnome.org/show_bug.cgi?id=755950)**
## Description
>>>
I was unable to find this feature in Meld, so I am making a request for it. I would not go into detail explaining how this works in other editors, but rather provide two links, that demonstrate what it is.
https://notepad-plus-plus.org/features/column-mode-editing.html
http://stackoverflow.com/questions/1802616/how-to-select-columns-in-editors-notepad-kate-vim-sublime-textpad-etc-an
Since Meld is usually used by programmers, column mode would be very handy, for example when you want to comment out may consecutive lines.
>>>https://gitlab.gnome.org/GNOME/meld/-/issues/77[BZ#738700] Add "Patience Diff" diff2020-03-03T20:27:16ZBugzilla[BZ#738700] Add "Patience Diff" diff## Submitted by Konstantine Rybnikov
**[Link to original bug (#738700)](https://bugzilla.gnome.org/show_bug.cgi?id=738700)**
## Description
>>>
There's wonderful diff algorithms called Patience Diff [0], which is used, for example, ...## Submitted by Konstantine Rybnikov
**[Link to original bug (#738700)](https://bugzilla.gnome.org/show_bug.cgi?id=738700)**
## Description
>>>
There's wonderful diff algorithms called Patience Diff [0], which is used, for example, by tool called patdiff [1]. It seems to be much more developer-friendly, so I'd like to propose to use that, either as an option or just as main algorithm (not sure what's best).
Thanks!
[0]: http://bramcohen.livejournal.com/73318.html?nojs=1
[1]: http://neocontra.blogspot.com/2013/02/public-service-announcement-patdiff-is.html
>>>https://gitlab.gnome.org/GNOME/meld/-/issues/24[BZ#635593] Newline differences should be displayed and highlighted2020-03-28T00:47:23ZBugzilla[BZ#635593] Newline differences should be displayed and highlighted## Submitted by Kai Willadsen
**[Link to original bug (#635593)](https://bugzilla.gnome.org/show_bug.cgi?id=635593)**
## Description
>>>
See [bug 602933](https://bugzilla.gnome.org/show_bug.cgi?id=602933).
The idea is that when a n...## Submitted by Kai Willadsen
**[Link to original bug (#635593)](https://bugzilla.gnome.org/show_bug.cgi?id=635593)**
## Description
>>>
See [bug 602933](https://bugzilla.gnome.org/show_bug.cgi?id=602933).
The idea is that when a newline character is part of a difference (in particular unicode newlines) it would be useful to have some way of showing that the newline characters are different.
At the moment, Meld discards line ending information and considers all newline characters/sequences to be equal. However, we can keep it around with splitlines(). It's not entirely clear in which situations we should take into account newline differences.
>>>https://gitlab.gnome.org/GNOME/meld/-/issues/442An option to ignore BOM2020-04-15T21:23:02ZJohnAn option to ignore BOMI have two identical files, one in UTF-8 and another in UTF-8-with-BOM. When I compare them with Meld, it treats them as different.
Trying to fix it, I have added `\uFEFF` in text filters, but it breaks directory comparison.
Another at...I have two identical files, one in UTF-8 and another in UTF-8-with-BOM. When I compare them with Meld, it treats them as different.
Trying to fix it, I have added `\uFEFF` in text filters, but it breaks directory comparison.
Another attempt was to use `\xEF\xBB\xBF`, but it doesn't help to ignore the BOM.
That is,
* I don't know how to fix this problem for myself
* Even if someone could help me with more advanced regex, it will be better to make it available for new users out of the box.
Meld 3.20.2 on Windows.
![meld](/uploads/896a0d59369bbc9dcc8dc8f723ddbd88/meld.png)https://gitlab.gnome.org/GNOME/meld/-/issues/114[BZ#771752] No UI button/icon to replace target lines with nothing, when sour...2020-04-30T21:34:31ZBugzilla[BZ#771752] No UI button/icon to replace target lines with nothing, when source is empty## Submitted by Dan Dascalescu
**[Link to original bug (#771752)](https://bugzilla.gnome.org/show_bug.cgi?id=771752)**
## Description
>>>
Created attachment 335979
Replace extra lines with nothing
If the right file has some extra l...## Submitted by Dan Dascalescu
**[Link to original bug (#771752)](https://bugzilla.gnome.org/show_bug.cgi?id=771752)**
## Description
>>>
Created attachment 335979
Replace extra lines with nothing
If the right file has some extra lines compared to the left, and I want to "replace" those lines with the virtually empty lines "in" the file to the left, there's no UI to do so. I must manually delete the lines from the right file.
I believe WebStorm's visual diff tool has a better approach that we could emulate - please see the screenshot.
**Attachment 335979**, "Replace extra lines with nothing":
![No_control_to_replace_lines_with_nothing](/uploads/246653ff5b00cd7edf747b93d6b3693e/No_control_to_replace_lines_with_nothing.png)
>>>https://gitlab.gnome.org/GNOME/meld/-/issues/469Feature request: An option to start with one-side-only folders collapsed2020-05-15T21:03:13ZMarkus-NFeature request: An option to start with one-side-only folders collapsedWhen doing a folder comparison, I'm usually not interested in the contents of folders that exist on the left (or right) side only. And if there are many of them, I have to collapse them all manually in order to make the tree view shorter...When doing a folder comparison, I'm usually not interested in the contents of folders that exist on the left (or right) side only. And if there are many of them, I have to collapse them all manually in order to make the tree view shorter and better to handle. And I'll have to do it again after every "Refresh View". So it would be helpful if I could choose the behaviour on startup , and it should also apply on "Refresh View".https://gitlab.gnome.org/GNOME/meld/-/issues/472Current selection lost on Windows2020-06-20T23:59:27ZCarlo MarchioriCurrent selection lost on WindowsHello,
I'm running Meld on Windows 10.
It works great.
Only, when I mark a conflict as resolved, some background tasks a run (black cmd windows)
and eventually the current selection gets lost and the first file in the list become select...Hello,
I'm running Meld on Windows 10.
It works great.
Only, when I mark a conflict as resolved, some background tasks a run (black cmd windows)
and eventually the current selection gets lost and the first file in the list become selected.
Thanks, Carlo.https://gitlab.gnome.org/GNOME/meld/-/issues/483Feature: split `NEW` directory filter into `NEW at right` and `NEW at left`2020-06-25T23:36:26ZFrankyFeature: split `NEW` directory filter into `NEW at right` and `NEW at left`When you are comparing 2 directories, if you just care what is at the left directory that is not on the right directory (or vice versa), it would be handy to filter just what is new from one way. If you care what is new from both sides y...When you are comparing 2 directories, if you just care what is at the left directory that is not on the right directory (or vice versa), it would be handy to filter just what is new from one way. If you care what is new from both sides you cold just mark both filters.
As a case of use, I am creating a code-generator that generates code for a framework, so when I use meld to see the new files I get the whole screen full of files that are in the framework but not in the generator output (since I generate far fewer files than the ones that already exists on the framework) and searching for the files that are only on the generator output is quite hard.https://gitlab.gnome.org/GNOME/meld/-/issues/348Error message at start of Meld 3.20.0 on Windows: "Please Insert a Disk into ...2020-07-14T06:59:56ZGhost UserError message at start of Meld 3.20.0 on Windows: "Please Insert a Disk into Drive"Hi.
The neu Version of Meld forces a error-window:
Please Insert a Disk into Drive \Device\harddisk6\Dr6"
Please Insert a Disk into Drive \Device\harddisk2\Dr2"
Please Insert a Disk into Drive \Device\harddisk4\Dr4"
for 20 times on ...Hi.
The neu Version of Meld forces a error-window:
Please Insert a Disk into Drive \Device\harddisk6\Dr6"
Please Insert a Disk into Drive \Device\harddisk2\Dr2"
Please Insert a Disk into Drive \Device\harddisk4\Dr4"
for 20 times on every start of meld on a Windows7-64Bit computer.
Meld V3.20.0 is starting normaly after this.
The old version doesn't do that!
I disable a build-in cardreader, who has some logical drives for sd-cards..., but this doesn't solve the problem.
In Procmon, i can't see a access to the logical drives, so i think it has a other reason.
All Network folders are accessable.
What (device) is Meld accessing on the start?https://gitlab.gnome.org/GNOME/meld/-/issues/479Scrolling issue...2020-07-21T01:40:01ZbarcarollerScrolling issue...Attached you will find two C files (from nDPI). If you run meld to compare the two files, you will see that meld will not allow you to scroll through the last block at the end of the files (regardless of whether you use the mouse button...Attached you will find two C files (from nDPI). If you run meld to compare the two files, you will see that meld will not allow you to scroll through the last block at the end of the files (regardless of whether you use the mouse buttons, mouse-wheel, or keyboard).
Using meld 3.20.2 and Python 3.7.6 on 64-bit Fedora 31
[aaa](/uploads/8886585c437b29fa85eb5f32df728a3d/aaa)
[bbb](/uploads/15832f41dfc8e8109e8c932d67f79b5f/bbb)https://gitlab.gnome.org/GNOME/meld/-/issues/495No encoding settings at Windows Meld 3.20.22020-08-13T23:38:29ZSecretU4No encoding settings at Windows Meld 3.20.2## OS information
* OS : Windows 10 pro 1909
* System Language : Korean
## Main Problem
1. Windows users cannont access Meld's detect encoding options at `Meld/Preferences`
2. It makes Meld only detect `UTF-8` encoding, so Meld can't ...## OS information
* OS : Windows 10 pro 1909
* System Language : Korean
## Main Problem
1. Windows users cannont access Meld's detect encoding options at `Meld/Preferences`
2. It makes Meld only detect `UTF-8` encoding, so Meld can't detect file's encoding with other encoding like `EUC-KR`, `Shift-JIS`
3. At file with other encoding, Meld detect file's encoding `CP-1252`, first encoding at alphabetically arranged encoding name list.
## Possible Solution
* Make new section about encoding at `Meld_Preferences`
1. Meld already has function about possible detect encoding list.
2. You can make registry to activate it.
### Possible Registry Info
* Name : `detect-encodings`
* Type : `REG-SZ`
* Data Format : `list` object containing encoding name consisted `str` object
example : `['UTF-8','EUC-KR','UTF-16']`
## Releated Issues
### Reported at Issue Tracker
#350
### Reported at Internet
* https://stackoverflow.com/questions/38919384/configure-meld-encoding-to-cp-1252
* https://qastack.kr/ubuntu/839755/meld-shows-output-in-unreadable-alphabet-japanese-chinese
This site seems multi-language supported, but I cannot find its english domain. Sorry.https://gitlab.gnome.org/GNOME/meld/-/issues/494Shading background for read-only pane2020-08-22T01:56:48ZAnatoli BabeniaShading background for read-only paneIf some file is read-only on `meld`, the only indication is the lock icon in the top near the filename. It would help to change the background to make it visually obvious before user tries to find the reason if some edit fails.
![image]...If some file is read-only on `meld`, the only indication is the lock icon in the top near the filename. It would help to change the background to make it visually obvious before user tries to find the reason if some edit fails.
![image](/uploads/b4c276f180f209bdce852c457d499443/image.png)https://gitlab.gnome.org/GNOME/meld/-/issues/505Format as Patch doesn't incorporate changes from synchronization point.2020-10-03T22:11:49ZNicholas RishelFormat as Patch doesn't incorporate changes from synchronization point.Before synchronization points added:
![image](/uploads/e5ec99c1d5cfccc9bd26f2f4b460daa1/image.png)
After Synchronization points added:
![image](/uploads/fbccff5d1077cb567cd13ee7e56ca386/image.png)
Generated Patch (before and after)
```...Before synchronization points added:
![image](/uploads/e5ec99c1d5cfccc9bd26f2f4b460daa1/image.png)
After Synchronization points added:
![image](/uploads/fbccff5d1077cb567cd13ee7e56ca386/image.png)
Generated Patch (before and after)
```
@@ -633,17 +633,23 @@
return OPERATOR_PASS_THROUGH;
}
+ /* apply movement, then we're done */
+ view_pan_apply(C, op);
+ view_pan_exit(op);
+
+ return OPERATOR_FINISHED;
+}
+
+/* this operator only needs this single callback, where it calls the view_pan_*() methods */
+static int view_scroll_down_exec(bContext *C, wmOperator *op)
+{
PropertyRNA *prop = RNA_struct_find_property(op->ptr, "page");
if (RNA_property_is_set(op->ptr, prop) && RNA_property_boolean_get(op->ptr, prop)) {
ARegion *region = CTX_wm_region(C);
RNA_int_set(op->ptr, "deltay", region->v2d.mask.ymin - region->v2d.mask.ymax);
}
- /* apply movement, then we're done */
- view_pan_apply(C, op);
- view_pan_exit(op);
-
- return OPERATOR_FINISHED;
+ return view_scroll_vertical_apply(C, op);
}
static void VIEW2D_OT_scroll_down(wmOperatorType *ot)
```https://gitlab.gnome.org/GNOME/meld/-/issues/237Add "line interval selection" based file diff feature2020-10-16T12:18:27ZpgpAdd "line interval selection" based file diff featureIt may happen the need to compare big code files, when the actual necessity is just to compare a few functions in these files (clearly, the files could differ -even a lot- in other parts, and we are not interested in these ones, this may...It may happen the need to compare big code files, when the actual necessity is just to compare a few functions in these files (clearly, the files could differ -even a lot- in other parts, and we are not interested in these ones, this may happen when doing refactoring or porting from legacy code). Without doing copy/paste into different files every time, a line interval selector in the diff view would be useful in order to allow comparing only relevant intervals of the two files (e.g. choosing lines l1 to l2 of file 1 to be compared against lines l3 to l4 of file 2).https://gitlab.gnome.org/GNOME/meld/-/issues/506Allow selecting lines by clicking and/or draging line numbers2020-10-17T07:38:17ZLeo WanderslebAllow selecting lines by clicking and/or draging line numbersIn Meld there is only a few pixel wide space between the light grey background and the horizontal center of the first (in programming usually invisible character). If I drag further to the left, nothing gets selected. If I drag further t...In Meld there is only a few pixel wide space between the light grey background and the horizontal center of the first (in programming usually invisible character). If I drag further to the left, nothing gets selected. If I drag further to the right, I miss the first character of the first line.
In other editors like Android Studio, to select line 100 to 120, I can click and drag down on the line numbers or the background around the line number outside the text field to select full lines. Please adopt this UX.https://gitlab.gnome.org/GNOME/meld/-/issues/30[BZ#644910] Compare archive files (tar.gz or zip)2020-11-03T19:20:55ZBugzilla[BZ#644910] Compare archive files (tar.gz or zip)## Submitted by say..@..com
**[Link to original bug (#644910)](https://bugzilla.gnome.org/show_bug.cgi?id=644910)**
## Description
>>>
Sometimes you're editing files inside an archive (for example, OpenOffice files are zipped archiv...## Submitted by say..@..com
**[Link to original bug (#644910)](https://bugzilla.gnome.org/show_bug.cgi?id=644910)**
## Description
>>>
Sometimes you're editing files inside an archive (for example, OpenOffice files are zipped archives of XML files) and you want to compare the files inside. You could unarchive the files, compare the directories, and rearchive as necessary. But if you want to make quick changes and test their effects, this adds a lot of time. It would be nice for meld to be able to access the files in the archive without unarchiving first.
This might be easy to implement using GVFS.
In terms of user interface, in the "Compare directory" dialog you could select a "Directory, or archive containing a directory".
>>>