Re: Sorting selections in MCEDIT
For more complex sorts you could set the mc sort order to Unsorted, then F9, Command, External panelize, then a regular unix sort command like ls | sort -t"_" -k3,3 let unix do the sort. On 5/23/22 7:16 AM, Ben wrote: I've searched all over the net, read the MCEDIT and MC man pages, pressed F1 in the proper context, and I can't find any reference to the sorting parameters for the OPTIONS/SORT command in MCEDIT. I tried a bunch of things to get it to reverse the default sort order, and finally found that "-r" would do it. Is there a reference anywhere, or could someone who is familiar with MCEDIT's internals, post what the options actually are? I'd love to be able to do more complex/specific sorts, particularly using specified parts of lines as the key rather than just from the first characters. TIA. ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Sorting selections in MCEDIT
I've searched all over the net, read the MCEDIT and MC man pages, pressed F1 in the proper context, and I can't find any reference to the sorting parameters for the OPTIONS/SORT command in MCEDIT. I tried a bunch of things to get it to reverse the default sort order, and finally found that "-r" would do it. Is there a reference anywhere, or could someone who is familiar with MCEDIT's internals, post what the options actually are? I'd love to be able to do more complex/specific sorts, particularly using specified parts of lines as the key rather than just from the first characters. TIA. ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Multiple patches with new functions for mcedit
Hi, I was coding my mcedit fork for some time and I've added c.a. 17 new functionalities to it. I've submitted all of them to upstream but all of them were rejected. So I thought of writing this email and offering them to anyone for $25 each. Here is the list of them, maybe you'll find something interesting? 1. Soft wraps - toggleable visual-only wrapping of lines that exceed the screen width. 2. Ack/Ag/Rg interface - a popup listing all matches allowing jumping to them. 3. Listing of objects (separate for functions, variables, types and all) from TAGS file allowing to jump to them. 4. Quick jumps to previous and next tag (to jump to preceding/following function). 5. Ctags completion - after indexing e.g.: GLib allows to complete all functions from it by entering g_, or functions from the project: 6. Remembering and restoration of last selections (marks). 7. Peek at prototype (ctrl-s, alt-? to jump to definition) - shows a small popup window with the prototype for function under cursor. 8. Slang scripting engine (plugins in ~/.config/mc/plugin, init script at …/mc/init.sl). Current plugins: - plugins/commentify.sl - toggles /*...*/ comment on current like, - plugins/grow_shrink_integer.sl - grows or decreases current number, - plugins/list-paragraphes.sl - lists all paragraphs and allows to jump to them, - plugins/read_file.sl - completes the file under cursor, e.g.: conf -> configure.ac, 10. Rich ExternalCommand window - new options and list of remembered commands: 11. Terminal window (called instruction station; ctrl-insert) - allows to run make, git, etc. 13. Fix WindowNext and …Prev to keep the order of windows unchanged. 14. Automatic grouping of headers and sources in the window list – headers precede their sources. 15. Window cascading (alt-ctrl-c) and tiling (alt-ctrl-t). 16. Centering of view (alt-c). 17. Periodic command (alt-shift-i) - a command that is executed every given number of seconds + number of keypresses. Good for regenerating TAGS file (it is reloaded automatically). -- Best regards, Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: Do your mcedit freeze for a moment, especially at file save?
On Fri, 25 Jun 2021, Sebastian Gniazdowski wrote: Yes, of course I'll disclose the bug. I only asked because I wanted to know that it isn't only me, that's all. Could someone confirm the issue? Thanks, that's helpful! Interesting that since the bug was introduced about 10 years ago nobody really noticed... -- Sincerely yours, Yury V. Zaytsev ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: Do your mcedit freeze for a moment, especially at file save?
Yes, of course I'll disclose the bug. I only asked because I wanted to know that it isn't only me, that's all. Could someone confirm the issue? The bug is: lack of row increasing leading to infinite loop interruptible by a keypress only: │ --- a/src/editor/editdraw.c 16│ +++ b/src/editor/editdraw.c 17│ @@ -926,14 +926,15 @@ render_edit_text (WEdit * edit, long start_row, long start_column, long e 18│ upto = MIN (curs_row - 1, end_row); 19│ while (row <= upto) 20│ { 21│ if (key_pending (edit)) 22│ return; 23│ edit_draw_this_line (edit, b, row, start_column, end_column); 24│ b = edit_buffer_get_forward_offset (>buffer, b, 1, 0); 25│ +row += 1; 26│ } On Fri, 25 Jun 2021 at 11:03, Yury V. Zaytsev wrote: > So maybe you’d care to disclose what the bug was and how did you fix it? > There is a general problem with input parsing, which can lead to effects > like this, but there are no known mcedit specific bugs of such sort. > > Sent from my iPad > > On 25. Jun 2021, at 09:59, Sebastian Gniazdowski via mc > wrote: > > > Hi! > I think that I've found a bug in mcedit which is: at save the UI freezes > for 2…5 secs, and is likely to become quicker unlocked if one will bang > enter rapidly. I wonder if only I have been occurring this issue? After > fixing the bug in my fork it is much better now. > > -- > Best regards, > Sebastian Gniazdowski > > ___ > mc mailing list > https://mail.gnome.org/mailman/listinfo/mc > > -- Best regards, Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: Do your mcedit freeze for a moment, especially at file save?
So maybe you’d care to disclose what the bug was and how did you fix it? There is a general problem with input parsing, which can lead to effects like this, but there are no known mcedit specific bugs of such sort. Sent from my iPad > On 25. Jun 2021, at 09:59, Sebastian Gniazdowski via mc wrote: > > > Hi! > I think that I've found a bug in mcedit which is: at save the UI freezes for > 2…5 secs, and is likely to become quicker unlocked if one will bang enter > rapidly. I wonder if only I have been occurring this issue? After fixing the > bug in my fork it is much better now. > > -- > Best regards, > Sebastian Gniazdowski > > ___ > mc mailing list > https://mail.gnome.org/mailman/listinfo/mc ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Do your mcedit freeze for a moment, especially at file save?
Hi! I think that I've found a bug in mcedit which is: at save the UI freezes for 2…5 secs, and is likely to become quicker unlocked if one will bang enter rapidly. I wonder if only I have been occurring this issue? After fixing the bug in my fork it is much better now. -- Best regards, Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Is there a way to tell mcedit to start in window mode instead of full screen?
Hi, the options for a cascade (-w/--cascade) and tiling (-T/--tile) arrangement are implemented in https://midnight-commander.org/ticket/4184 patch. Also, menu entries (in Window submenu) are added. You can test the patch, if you like, it would help. On Sat, 16 Jan 2021 at 10:10, bcurrey99 wrote: > The cascading windows is a very nice idea because you could see all of the > files that were opened. > > But if that is too difficult, dividing the screen into two rows of tiled > windows (maximum 6 or 8) would be reasonable . > > Thanks much for your better idea. > Bob Currey > > > Sent from my Galaxy > > > Original message > From: Sebastian Gniazdowski via mc > Date: 1/16/21 9:13 AM (GMT-06:00) > To: mc@gnome.org > Subject: Re: mcedit: Is there a way to tell mcedit to start in window mode > instead of full screen? > > (I'm replying to the list this time, just ensuring that it's not missed) > > Can I ask for clarification: > - when an option, -w for example, will be given, > - then mc should start with the file's window in windowed (not fullscreen > mode), > - for multiple files, possibly arranged the windows in e.g.: cascading way, > ? > > I think that this would involve first creating a CK_WindowCascade action > that would arrange the windows (first exiting fullscreen if needed). > > On Fri, 15 Jan 2021 at 14:32, Bob Currey via mc wrote: > >> I looked on the --help screen but didn't see an option to open in window >> mode >> >> $ mcedit --help >> Usage: >> mcedit [OPTION…] [+lineno] file1[:lineno] [file2[:lineno]...] >> >> >> GNU Midnight Commander 4.8.25-154-g33c84e75e >> >> >> Help Options: >> -h, --helpShow help options >> --help-allShow all help options >> --help-terminal Terminal options >> --help-color Color options >> >> Application Options: >> -V, --version Displays the current version >> -f, --datadir Print data directory >> -F, --datadir-infoPrint extended info about used data >> directories >> --configure-options Print configure options >> -P, --printwd= Print last working directory to specified file >> -U, --subshellEnables subshell support (default) >> -u, --nosubshell Disables subshell support >> -l, --ftplog= Log ftp dialog to specified file >> -v, --view= Launches the file viewer on a file >> -e, --edit= ... Edit files >> >> >> Please send any bug reports (including the output of 'mc -V') >> as tickets at www.midnight-commander.org >> >> Midnight Commander is my favorite "mst have" program on my Linux >> machines. >> >> Thanks for all your efforts :) >> >> Bob Currey >> >> >> ___ >> mc mailing list >> https://mail.gnome.org/mailman/listinfo/mc >> > > > -- > Sebastian Gniazdowski > > -- Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
On Thu, 21 Jan 2021 at 12:51, Yury V. Zaytsev wrote: > On Thu, 21 Jan 2021, Sebastian Gniazdowski wrote: > > > I have made the wish list on the ticket system: > > http://midnight-commander.org/ticket/4177 > > > > Are there any interesting entries? Or: is the direction in them > > compliant with the maintainer vision? > > Sorry, I've used up the time that I can make for mc for the coming months, > but to make it short, I'd rather side with Andrew. > > I'm pretty averse to overloading mcedit with small hardly discoverable > functions (however useful they are), and bolting on a questionable > scripting engine on top of that. > There are two arguments in the paragraph: 1. Small hardly discoverable features: 2. Questionable scripting engine. Ad. 1. I think/I'm hoping that it's just a first impression that the wishlist has made, mostly because of how long it is. I think that the entries in it are of the following categories: A. Small bugfixes. Like the whitespace leaving on the divided line by the typewriter wrapping, or the pasting onto an input's initial, faded text, or the find definition goto-line instead of replacing the file with the same file, or the fix of ParagraphFormat action, etc. Such changes are fine as they are rather bugfixes than microchanges, and bugs can be as small as they can get, because they're bugs that should be just fixed. B. New features that are narrow, but sensible. Like the line joining (vim's J command), character swapping (Ctrl-t in readline), centering of view (vim's zz command), CapitalizeWord (vim's gUiw command), LowercaseWord/Letter, ReloadFile action (vim's :edit), or the to-open-paren indenting, etc. I think that such changes are yes – narrow – however they're have a good history in other editors, so it's fine to implement them. All of them require only small coding. C. Features by the big F – with big coding required by them. Like the (30) alternate/updated WindowList command merging (but with a separation) the entries of the open file list and the editor history, or the clipboard history, (61) showing of current function in the window bar, or the (10) word-delimited block paren-like matching (i.e.: MatchBracket action), MultiSearch listbox filtering, etc. Such changes are IMO little heavy and require acceptance of the maintainer, however I strongly believe in them (not sure if all such wishes from the list, however the above – yes) and I hope that I'll win maintainers blessing on them. D. Annoyance resolving changes. Like the (52) WordRight to jump to the end of word, not to the beginning of next word, or (41) repeating of Complete to move the selection in the list to next item, or (46) opening of file without adding it to editor history, or (53) explicit jumps to previous locations in the file, (56) saving and restoring of the replaced buffer's undo history. I think that such changes may be most difficult to convey to the maintainer. On the other hand, SearchOppositeContinue has found its way to mcview, and it is from this category – a narrow change to resolve an annoying problem, so maybe there's hope. E. Fancy changes. Like (13) completion of file paths in buffer, (39) go-to filename under the cursor, (40) repeating of all characters and commands from the last save, (57) peek of the declaration of the function under the cursor, or the terminal window support, or (18) bookmark listbox, (32) search results listbox, etc. Such changes can be perceived as controversial because of the fanciness and size of the patches. I think that they need to be "pulled off", which makes them open for a simple rejection. F. Creative, eccentric changes. Like the (17) preview of ExternalCommand, (14) tray with a set of Unicode symbols, (16) git support, (58) a tags aware window list. Such changes are rather doomed for a fork fate. 17 and 14 – yes, maybe, but the git support or 58 – no, rather no chances of acceptance of the maintainer. G. Long awaited changes. Like (5) file browse widget for Edit/SaveFile,(15) "other file" .c ↔ .h support, (11) CK_WindowCascade / CK_WindowTile, (29) scroll left/right. Such changes are IMO problematic, because they're known for the maintainer and fossilized. I however still have hopes for all of the above, especially the last three. H. Weird changes Such changes might be the ones that you and Andrew have biggest objections to, like 45, 36, 31, 4, 24, 47, etc. I've included them in the wishlist just to stimulate the grey cells and new ideas. They and the ones from F. may have caused the allergic reaction of Andrew… And also D., contributing to the microchanges aura. Ad.2. Questionable scripting. Slang is a good language. It e.g.: allows inheritance of structures via, e.g.: car = struct {x, y, z}; truck = struct {@car, t}; Slirp is a very reliable tool. Did maybe the kitchensink example scare you off? Because it's the standard syntax used
Re: mcedit: Center current line in middle of screen
On Thu, 21 Jan 2021, Sebastian Gniazdowski wrote: I have made the wish list on the ticket system: http://midnight-commander.org/ticket/4177 Are there any interesting entries? Or: is the direction in them compliant with the maintainer vision? Sorry, I've used up the time that I can make for mc for the coming months, but to make it short, I'd rather side with Andrew. I'm pretty averse to overloading mcedit with small hardly discoverable functions (however useful they are), and bolting on a questionable scripting engine on top of that. There are enough fundamental problems with mc codebase, and my vision for it would have been to clean up the core, cover it with tests, and expose its API to an external engine, which provides a high level memory managed language. Everything beyond core could be pushed into this layer and left up to users and distributions... This was pretty much what mc^2 was a prototype for, but very unfortunately we didn't have the capacity to integrate it :-( -- Sincerely yours, Yury V. Zaytsev ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
On number 5, the file dialog widget is needed for :Open file...Save as...Insert file...Copy to file...Adding this should close ticket #2937.I noticed your references to macro languages and Jed. I used to use Brief and loved its macro language. I still have a working copy that can run on linux with all my macros. The macro language gave it tremendous power and flexibility. Bob Currey Sent from my Galaxy Original message From: Sebastian Gniazdowski via mc Date: 1/20/21 5:27 PM (GMT-06:00) To: "Yury V. Zaytsev" Cc: mc@gnome.org Subject: Re: mcedit: Center current line in middle of screen Hi,I have made the wish list on the ticket system: http://midnight-commander.org/ticket/4177Are there any interesting entries? Or: is the direction in them compliant with the maintainer vision? -- Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
Hi, I have made the wish list on the ticket system: http://midnight-commander.org/ticket/4177 Are there any interesting entries? Or: is the direction in them compliant with the maintainer vision? -- Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Is there a way to tell mcedit to start in window mode instead of full screen?
The cascading windows is a very nice idea because you could see all of the files that were opened.But if that is too difficult, dividing the screen into two rows of tiled windows (maximum 6 or 8) would be reasonable .Thanks much for your better idea. Bob Currey Sent from my Galaxy Original message From: Sebastian Gniazdowski via mc Date: 1/16/21 9:13 AM (GMT-06:00) To: mc@gnome.org Subject: Re: mcedit: Is there a way to tell mcedit to start in window mode instead of full screen? (I'm replying to the list this time, just ensuring that it's not missed)Can I ask for clarification:- when an option, -w for example, will be given,- then mc should start with the file's window in windowed (not fullscreen mode),- for multiple files, possibly arranged the windows in e.g.: cascading way,?I think that this would involve first creating a CK_WindowCascade action that would arrange the windows (first exiting fullscreen if needed).On Fri, 15 Jan 2021 at 14:32, Bob Currey via mc wrote: I looked on the --help screen but didn't see an option to open in window mode$ mcedit --helpUsage: mcedit [OPTION…] [+lineno] file1[:lineno] [file2[:lineno]...]GNU Midnight Commander 4.8.25-154-g33c84e75eHelp Options: -h, --help Show help options --help-all Show all help options --help-terminal Terminal options --help-color Color optionsApplication Options: -V, --version Displays the current version -f, --datadir Print data directory -F, --datadir-info Print extended info about used data directories --configure-options Print configure options -P, --printwd= Print last working directory to specified file -U, --subshell Enables subshell support (default) -u, --nosubshell Disables subshell support -l, --ftplog= Log ftp dialog to specified file -v, --view= Launches the file viewer on a file -e, --edit= ... Edit filesPlease send any bug reports (including the output of 'mc -V')as tickets at www.midnight-commander.orgMidnight Commander is my favorite "mst have" program on my Linux machines. Thanks for all your efforts :)Bob Currey___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc -- Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Is there a way to tell mcedit to start in window mode instead of full screen?
(I'm replying to the list this time, just ensuring that it's not missed) Can I ask for clarification: - when an option, -w for example, will be given, - then mc should start with the file's window in windowed (not fullscreen mode), - for multiple files, possibly arranged the windows in e.g.: cascading way, ? I think that this would involve first creating a CK_WindowCascade action that would arrange the windows (first exiting fullscreen if needed). On Fri, 15 Jan 2021 at 14:32, Bob Currey via mc wrote: > I looked on the --help screen but didn't see an option to open in window > mode > > $ mcedit --help > Usage: > mcedit [OPTION…] [+lineno] file1[:lineno] [file2[:lineno]...] > > > GNU Midnight Commander 4.8.25-154-g33c84e75e > > > Help Options: > -h, --helpShow help options > --help-allShow all help options > --help-terminal Terminal options > --help-color Color options > > Application Options: > -V, --version Displays the current version > -f, --datadir Print data directory > -F, --datadir-infoPrint extended info about used data directories > --configure-options Print configure options > -P, --printwd= Print last working directory to specified file > -U, --subshellEnables subshell support (default) > -u, --nosubshell Disables subshell support > -l, --ftplog= Log ftp dialog to specified file > -v, --view= Launches the file viewer on a file > -e, --edit= ... Edit files > > > Please send any bug reports (including the output of 'mc -V') > as tickets at www.midnight-commander.org > > Midnight Commander is my favorite "mst have" program on my Linux > machines. > > Thanks for all your efforts :) > > Bob Currey > > > ___ > mc mailing list > https://mail.gnome.org/mailman/listinfo/mc > -- Sebastian Gniazdowski ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
Hi Sebastian, thank you for sharing this! In fact, I also digged into the source and made a quick fix for my needs before I read your last message. I was surprised how well the API is crafted, so changing small things directly in the C source code is probably the way to go for minor features like this. > I'm thinking that such feature has a minor drawback which can be > additionally addressed – it is little offensive, IMO, to human brain > to observe such jumps. Personally, I have no need for moving the display slowly or gradually, I think this adds complexity. I am a fan of minimalism but fully respect any efforts to make software more accessible. So I am curious if you come up with some changes here, would be interesting. There is major difference in my patch however — and this is important for my personal text editing experience: I mostly feel the need to center the current line when I am already at the bottom of the buffer, eg. editing long text or code and the cursor line is both on the bottom of the window and the buffer. Therefore I made a hack to redraw the window when I am in the bottom half of both window and buffer. Btw, I was also long-time vim and emacs user, but got fed up with many things in both editors, especially with the complexity and bloat which came with third-party packages and extensions. That is why I am still looking for a replacement and mcedit is indeed on the very top of my list. Anyhow, I will upload my patch to your ticket, please feel free to delete/reuse/modify it for your proposed changes. Kind regards, Martin ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
mcedit: Is there a way to tell mcedit to start in window mode instead of full screen?
I looked on the --help screen but didn't see an option to open in window mode $ mcedit --help Usage: mcedit [OPTION…] [+lineno] file1[:lineno] [file2[:lineno]...] GNU Midnight Commander 4.8.25-154-g33c84e75e Help Options: -h, --help Show help options --help-all Show all help options --help-terminal Terminal options --help-color Color options Application Options: -V, --version Displays the current version -f, --datadir Print data directory -F, --datadir-info Print extended info about used data directories --configure-options Print configure options -P, --printwd= Print last working directory to specified file -U, --subshell Enables subshell support (default) -u, --nosubshell Disables subshell support -l, --ftplog= Log ftp dialog to specified file -v, --view= Launches the file viewer on a file -e, --edit= ... Edit files Please send any bug reports (including the output of 'mc -V') as tickets at www.midnight-commander.org Midnight Commander is my favorite "mst have" program on my Linux machines. Thanks for all your efforts :) Bob Currey ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
On Fri, 15 Jan 2021 at 10:58, Yury V. Zaytsev wrote: > Sebastian, if you are motivated and have time to do some serious work on mc, maybe we should talk about a vision first? Thanks for the invite! Yes I'm motivated, I find it very entertaining to work on mc. I wish someone had taken the time instead to integrate the Lua fork by > mooffie. Unfortunately he wasn't up to maintaining his work of a genius > (no kidding) and we don't have resources to take it over. I think that he had one initial mistake, if I can say so – he scripted mc and not mcedit. I think that it's an editor that can gain most of a scripting engine, not a filemanager. > In as far as S-Lang scripting is concerned, it's definitively easy to bolt > it on, but I really wouldn't want to live with the resulting mess. Our > code base is already in a shape bad enough... > I have a very pleasant experience with S-Lang. I've ran my first script displaying a listbox from script after ~2 hours of hacking – thanks to Slirp, the S-Lang version of Swig. It works very, surprisingly well! And it has all the advanced features of Swig (take a look at examples/kitchensink/slirprc if you have time). It looks solid. Basically, to simply export a function to S-Lang, all that is required is to run: slirp header.h, with the declaration in that file and to compile and link the resulting header_glue.c (that slirp automatically creates)! What concerns me about S-Lang is that it's not an object oriented language and that it doesn't have a bool type. However, that might be a good thing, as the engine and the vision will be light thanks to this, maybe… It doesn't make sense to me for you invest your valuable time only to get > your patches criticized or rejected or just rotting on the tracker without > any feedback. If we can agree on a direction, then I think it will be good > for all of us, if we can't - at least it will be good for you, because > then you can spare your time arguing with us and directly setup a fork > instead... :-) > Yes, I had such hunches too. So my intentions are: – to make the gem, that mcedit is, more popular, – to make it grow and flourish mainly by the light scripting engine, but also by regular C work (like e.g.: the tags objects in listboxes patch – really, I don't know how I was using the various Vim tags plugins for years, as it's the mcedit's way – a simple listbox (which can be just built in) – that is the right way to do tags :) – then to utilize the scripting also in regular mc and see what ideas will come up. I'm constantly having ideas on mcedit improvements. I'm saving them to a file… It had like 80 entries, but I've just accidentally deleted it hours ago via a miserable rm -f **/*.#* glob (it expands to all files, not just those with hash in them, so look out) :( however I have a backup that has ~50 entries, uf … So maybe I could do a wish list on the wiki out of it? PS. This gives an idea for an improvement – a saving of the backup file to a predefined directory outside the current tree… Could be done as a script plugin, maybe. -- > Sincerely yours, > Yury V. Zaytsev > -- Sebastian Gniazdowski IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zinit Blog: http://zdharma.org ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
On Fri, 15 Jan 2021, Sebastian Gniazdowski via mc wrote: I'm also working on adding a S-Lang scripting to it :) It already works on my machine. It was really simple, just invoking SLang_init_all() and that was it, as libslang is already linked :) I have a plugin in it that implements adding and subtracting from number under cursor, for example. When I improve the support (e.g.: add some more S-Lang interface functions that would allow e.g.: moving the vie`w) I submit the patch. I wish someone had taken the time instead to integrate the Lua fork by mooffie. Unfortunately he wasn't up to maintaining his work of a genius (no kidding) and we don't have resources to take it over. In as far as S-Lang scripting is concerned, it's definitively easy to bolt it on, but I really wouldn't want to live with the resulting mess. Our code base is already in a shape bad enough... Sebastian, if you are motivated and have time to do some serious work on mc, maybe we should talk about a vision first? It doesn't make sense to me for you invest your valuable time only to get your patches criticized or rejected or just rotting on the tracker without any feedback. If we can agree on a direction, then I think it will be good for all of us, if we can't - at least it will be good for you, because then you can spare your time arguing with us and directly setup a fork instead... :-) -- Sincerely yours, Yury V. Zaytsev ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
I've finished coding the support, see https://midnight-commander.org/ticket/4175 for a patch. I'm thinking that such feature has a minor drawback which can be additionally addressed – it is little offensive, IMO, to human brain to observe such jumps. I feel this way basing on the relief that I've noticed when I moved from Vim to MCEdit recently. I was doing "zz" command very often there. I would guess that this has something to do with "rapidly changing pictures" topic in neurobiology. To address this, I propose an enhancement: to move display little slowly, gradually, just to not rudely cut the states of before and after the move. I could use the timers but I've noticed that timer.c has been removed recently. Why? ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
PS. There's one more patch that I hope will be accepted (after I improve it according to style guide): https://midnight-commander.org/ticket/4160 On Fri, 15 Jan 2021 at 11:05, Sebastian Gniazdowski wrote: > On Thu, 14 Jan 2021 at 15:24, wrote: > >> Hi there, >> >> to me, mcedit is a hidden gem. > > > For me too. It is so good that I've started to improve it recently. See my > pending patches: > > - https://midnight-commander.org/ticket/4165 > - http://midnight-commander.org/ticket/4169 > - http://midnight-commander.org/ticket/4174 > - http://midnight-commander.org/ticket/4171 > > I'm also working on adding a S-Lang scripting to it :) It already works on > my machine. It was really simple, just invoking SLang_init_all() and that > was it, as libslang is already linked :) I have a plugin in it that > implements adding and subtracting from number under cursor, for example. > When I improve the support (e.g.: add some more S-Lang interface functions > that would allow e.g.: moving the view) I submit the patch. > > It struck the right balance between ease of use, advanced features and >> simplicity. > > > Exactly. And IMO with a light scripting engine it could shine even more > and be able to compete with other main editors. > > However, I miss an important >> function: The ability to center the current line in the middle of the >> screen. I could not find it anywhere, maybe someone from the community >> can help? >> > > This is one of the most missed features by me and it was one of the main > things that drove me to contribute to mc. Seeing that someone shares my > view, I'll not wait until the scripting engine will be ready and I'll > implement the centering in C ("CenterView", perhaps, for the name of the > command?). It'll be there soon :) > > -- > Sebastian Gniazdowski > IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zinit > Blog: http://zdharma.org > -- Sebastian Gniazdowski IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zinit Blog: http://zdharma.org ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: Center current line in middle of screen
On Thu, 14 Jan 2021 at 15:24, wrote: > Hi there, > > to me, mcedit is a hidden gem. For me too. It is so good that I've started to improve it recently. See my pending patches: - https://midnight-commander.org/ticket/4165 - http://midnight-commander.org/ticket/4169 - http://midnight-commander.org/ticket/4174 - http://midnight-commander.org/ticket/4171 I'm also working on adding a S-Lang scripting to it :) It already works on my machine. It was really simple, just invoking SLang_init_all() and that was it, as libslang is already linked :) I have a plugin in it that implements adding and subtracting from number under cursor, for example. When I improve the support (e.g.: add some more S-Lang interface functions that would allow e.g.: moving the view) I submit the patch. It struck the right balance between ease of use, advanced features and > simplicity. Exactly. And IMO with a light scripting engine it could shine even more and be able to compete with other main editors. However, I miss an important > function: The ability to center the current line in the middle of the > screen. I could not find it anywhere, maybe someone from the community > can help? > This is one of the most missed features by me and it was one of the main things that drove me to contribute to mc. Seeing that someone shares my view, I'll not wait until the scripting engine will be ready and I'll implement the centering in C ("CenterView", perhaps, for the name of the command?). It'll be there soon :) -- Sebastian Gniazdowski IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zinit Blog: http://zdharma.org ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
mcedit: Center current line in middle of screen
Hi there, to me, mcedit is a hidden gem. It struck the right balance between ease of use, advanced features and simplicity. However, I miss an important function: The ability to center the current line in the middle of the screen. I could not find it anywhere, maybe someone from the community can help? I could image writing a work-around macro but before spending effort on this I was wondering if there are best practices. Also, the macro would not be so simple because I could not find a directive or definition to get the current line number. Doing this externally via `tput` or other tricks seems wrong and would it be even possible to combine external commands with internal instructions? Both while programming or writing longer texts, I often want to "center" my view and cursor and not being stuck on the last line of the screen. Most basic editors I know so far have this functionality on board (eg. nano --> C-L). Thank you for help on this in advance! Kind regards, Martin ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: How to switch from mcedit to mc file manager without closing editor?
> I tend to use a Konsole shell with 3 or 4 different tabs each running an instance of mc to edit multiple files at once. It's too hard to use GUI Konsole app in terminal on remote headless machine, instead of it I must use mc with single ssh instance. > Can't you switch back to the file manage window with Meta + ` ? Thanks!! This do the trick - show menu with opened windows, and allow switch back to file manager, also switch between documents! Strange, that I can't find this hotkey in mc documentation... On Tue, 23 Apr 2019 at 14:34, Yury V. Zaytsev wrote: > On Mon, 22 Apr 2019, Alexey Murz Korepov via mc wrote: > > > mcedit allow to open multiple files at once, but provide no build-in > > good interface for select seconf file to open - only window for manually > > write path to file. Is there any way exists to switch back into mc file > > manager panels from mcedit window without closing current file, to open > > second file for editing simultaneously both files? > > Can't you switch back to the file manage window with Meta + ` ? > > -- > Sincerely yours, > Yury V. Zaytsev > -- Best regards, Alexey Murz Korepov. E-mail: mur...@gmail.com Messengers: Matrix - https://matrix.to/#/@murz:ru-matrix.org Telegram - @MurzNN ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: How to switch from mcedit to mc file manager without closing editor?
On Mon, 22 Apr 2019, Alexey Murz Korepov via mc wrote: mcedit allow to open multiple files at once, but provide no build-in good interface for select seconf file to open - only window for manually write path to file. Is there any way exists to switch back into mc file manager panels from mcedit window without closing current file, to open second file for editing simultaneously both files? Can't you switch back to the file manage window with Meta + ` ? -- Sincerely yours, Yury V. Zaytsev ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: How to switch from mcedit to mc file manager without closing editor?
Hi Alexey, I tend to use a Konsole shell with 3 or 4 different tabs each running an instance of mc to edit multiple files at once. HTH Keith Roberts On 22/04/2019 19:10, Alexey Murz Korepov via mc wrote: mcedit allow to open multiple files at once, but provide no build-in good interface for select seconf file to open - only window for manually write path to file. Is there any way exists to switch back into mc file manager panels from mcedit window without closing current file, to open second file for editing simultaneously both files? -- Best regards, Alexey Murz Korepov. E-mail: mur...@gmail.com <mailto:mur...@gmail.com> Messengers: Matrix - https://matrix.to/#/@murz:ru-matrix.org Telegram - @MurzNN ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
%f macro in mcedit
Hi! My mc version: $ mc --version GNU Midnight Commander 4.8.19 System: Fedora 24 I just want to tell you that %f macro in mcedit is not correct. It contains the current file name that is selected in the panel but not the actual file name that is opened in mcedit. I created the mcedit item to run C++ program: += f \.cpp$ r Run clear app_path=/tmp/$(uuidgen) if g++ -o $app_path "%f"; then $app_path rm $app_path fi echo 'Press any key to exit.' read -s -n 1 Imagine that I opened the file a.cpp in mcedit. Then I pressed alt+` and switched to panel. Then I selected (or even opened in mcedit) the file b.cpp. Then I pressed alt+` and switched to mcedit with a.cpp. Then I executed the "Run" item from user menu. And... The b.cpp will be compiled and run. This is wrong! Why b.cpp??? I executed "Run" from a.cpp! I propose you to do the new macros for mcedit. %opened_file - the file name that is opened in current instance of mcedit. %opened_file_full_path - as %opened_file but full path to that file. I think that %opened_file may be not safe because the current directory may be changed in mc panel. So it is better to use %opened_file_full_path. %opened_file_dir - full path to directory where %opened_file is. %save - save opened file before executing the menu commands. May be useful in some cases. For example I don't want to press F2 every time before run changed code. Thanks for the mc. Best regards, Sergiy Vovk. ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit: undo warning
On Sun, 10 Sep 2017, Dmitry L. wrote: It looks like a bug for me. In mcedit I have next warning when remove block of text (when length is large than 16384): "Block is large, you may not be able to undo this action" But actually I can undo only when remove block of text with length less than 8190. So, when I remove block of text where 8190 <= length <=16384 I don't get any warning and can't undo this action. That's correct, the condition in question is (end_mark - start_mark) > option_max_undo / 2 where int option_max_undo = 32768 It looks like it should be option_max_undo / 4, according to your observation, but I have no idea why and how come... In any case, please report this bug on the Trac, because otherwise this will get lost on the list. -- Sincerely yours, Yury V. Zaytsev ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
mcedit: undo warning
Hello! It looks like a bug for me. In mcedit I have next warning when remove block of text (when length is large than 16384): "Block is large, you may not be able to undo this action" But actually I can undo only when remove block of text with length less than 8190. So, when I remove block of text where 8190 <= length <=16384 I don't get any warning and can't undo this action. PS: I'm using MCEdit 4.8.19 from Arch Linux repos -- //wbr, Dmitry L. ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: Local-to-dir mcedit prefs or quick profiles?
On 2/20/17, wwp <subscr...@free.fr> wrote: > I'm using mcedit to edit sources in many projects, some of them have > coding conventions that require [...] and some require [...] > > What feature or best practice would you suggest in order to quickly > switch mcedit settings (general editor options) according to the file > location? You can use mc^2 with a simple snippet like this: ui.Editbox.bind("<>", function(edt) if edt.filename and edt.filename:find "/projects/lambda/" then ui.Editbox.options.tab_size = 4 ui.Editbox.options.expand_tabs = true else ui.Editbox.options.tab_size = 8 ui.Editbox.options.expand_tabs = false end end) (For documentation, see [1]) (The 'else' case is needed because in MC the editor options are global, not local to each edit buffer.) mc^2 also comes with a modeline module (if you decide to use it just remember to require() it before the snippet above so it doesn't overwrite your settings). [1] http://www.typo.co.il/~mooffie/mc-lua/docs/html/classes/ui.Editbox.html#ui.Editbox.options ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: Local-to-dir mcedit prefs or quick profiles?
On Mon, 20 Feb 2017 11:24:48 +0100 (CET) "Yury V. Zaytsev" wrote: > On Mon, 20 Feb 2017, wwp wrote: > > > What feature or best practice would you suggest in order to quickly > > switch mcedit settings (general editor options) according to the file > > location? What do you guys do in such situation? (note that I'm using it > > for more 15 years, and decide to ask the community about this only now > > :-D ) > > Maybe we need some limited support for vim / emacs modelines... https://midnight-commander.org/ticket/3068 -- Andrew ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: Local-to-dir mcedit prefs or quick profiles?
Hello, On Mon, 20 Feb 2017 13:32:32 +0300 Andrew Borodin <aboro...@vmail.ru> wrote: > On Mon, 20 Feb 2017 11:24:48 +0100 (CET) "Yury V. Zaytsev" wrote: > > On Mon, 20 Feb 2017, wwp wrote: > > > > > What feature or best practice would you suggest in order to quickly > > > switch mcedit settings (general editor options) according to the file > > > location? What do you guys do in such situation? (note that I'm using it > > > for more 15 years, and decide to ask the community about this only now > > > :-D ) > > > > Maybe we need some limited support for vim / emacs modelines... > > https://midnight-commander.org/ticket/3068 I must say that the kate approach is probably less invasive towards the code (whatever mc could also support vim modelines), source code in where the use might not find those modelines or not be allowed to put them into. Regards, -- wwp pgpQ3bEQLevl7.pgp Description: OpenPGP digital signature ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: Local-to-dir mcedit prefs or quick profiles?
On Mon, 20 Feb 2017, wwp wrote: What feature or best practice would you suggest in order to quickly switch mcedit settings (general editor options) according to the file location? What do you guys do in such situation? (note that I'm using it for more 15 years, and decide to ask the community about this only now :-D ) Maybe we need some limited support for vim / emacs modelines... -- Sincerely yours, Yury V. Zaytsev ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Local-to-dir mcedit prefs or quick profiles?
Hello there, I'm using mcedit to edit sources in many projects, some of them have coding conventions that require the sources format to contain tabs (8-char wide tabs, 4-char, sometimes 2-) and some require tabs to be filled w/ spaces instead. mcedit works very well w/ this, but unless I use separate Unix accounts, I don't see how I could switch general editor options to match coding conventions (won't change options by hand every time). What feature or best practice would you suggest in order to quickly switch mcedit settings (general editor options) according to the file location? What do you guys do in such situation? (note that I'm using it for more 15 years, and decide to ask the community about this only now :-D ) Regards, -- wwp pgp1PxWZRbybj.pgp Description: OpenPGP digital signature ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
Re: mcedit: basic syntax file for rust language
On Tue, 4 Oct 2016, Laurent Wandrebeck wrote: Please find attached a syntax file to add (basic, and probably still a bit buggy) rust support. Could you please submit a patch via Trac, so it doesn't get lost on the mailing list? Many thanks! -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
mcedit: basic syntax file for rust language
Hi there, Please find attached a syntax file to add (basic, and probably still a bit buggy) rust support. Only addition needed to Syntax file is: file .\*\\.rs$ Rust\ssource include rust.syntax Please evaluate it for inclusion. Thanks, -- Laurent Wandrebeck# Syntax rules for the Rust programming language # black, blue, brightblue, brightcyan, brightgreen, brightmagenta, # brightred, brown, cyan, gray, green, lightgray, magenta, red, white, # yellow context default keyword whole auto yellow keyword whole break yellow keyword whole bool yellow keyword whole case yellow keyword whole char yellow keyword whole const yellow keyword whole continue yellow keyword whole crate brightgreen keyword whole do yellow keyword whole double yellow keyword whole else yellow keyword whole enum yellow keyword whole extern yellow keyword whole f32 yellow keyword whole f64 yellow keyword whole fn yellow keyword whole for yellow keyword whole goto yellow keyword whole i8 yellow keyword whole i16 yellow keyword whole i32 yellow keyword whole i64 yellow keyword whole if yellow keyword whole impl yellow keyword whole isize yellow keyword whole let brightmagenta keyword whole match yellow keyword whole mut brightgreen keyword whole pub yellow keyword whole register yellow keyword whole return yellow keyword whole self yellow keyword whole sizeof yellow keyword whole static yellow keyword whole str yellow keyword whole String yellow keyword whole struct yellow keyword whole switch yellow keyword whole trait yellow keyword whole u8 yellow keyword whole u16 yellow keyword whole u32 yellow keyword whole u64 yellow keyword whole unsafe red keyword whole use yellow keyword whole usize yellow keyword whole while yellow keyword whole ... yellow keyword whole linestart \{\s\t\}\[\s\t\]#*\n brightmagenta keyword whole \[\s\t\]default yellow keyword whole \[\s\t\]\{ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvwxyz\}\[0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvwxyz\]! white keyword whole => yellow keyword /// brown keyword //! brown keyword /\* black keyword \*/ black keyword // black keyword Option cyan keyword Some cyan keyword None cyan keyword Result brightcyan keyword Ok brightcyan keyword Err brightcyan keyword :: brightgreen keyword '\\\{"abtnvfr\}' brightgreen keyword '\\\{0123\}\{01234567\}\{01234567\}' brightgreen keyword '\\'' brightgreen keyword '' brightgreen keyword '\\0' brightgreen keyword '\{\s!"#$%&()\*\+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[]^_`abcdefghijklmnopqrstuvwxyz{|}~\}' brightgreen # punctuation characters, sorted by ASCII code keyword ! yellow keyword % yellow keyword && yellow keyword & brightmagenta keyword ( brightcyan keyword ) brightcyan keyword \* yellow keyword \+ yellow keyword , brightcyan keyword - yellow keyword / yellow keyword : brightcyan keyword ; brightmagenta keyword < yellow keyword = yellow keyword > yellow keyword ? brightcyan keyword [ brightcyan keyword ] brightcyan keyword ^ brightmagenta keyword { brightcyan keyword || yellow keyword | brightmagenta keyword } brightcyan keyword ~ brightmagenta context exclusive /// \n brown spellcheck context exclusive //! \n brown spellcheck # put in black because it does not follow rust automatic documentation guidelines context exclusive /\* \*/ black spellcheck # put in black because it does not follow rust automatic documentation guidelines context exclusive // \n black spellcheck context linestart # \n brightred keyword \\\n yellow keyword /\**\*/ brown keyword //*\n brown keyword "+" red keyword <+> red context " " green spellcheck keyword \\" brightgreen keyword %% brightgreen keyword %\[#0\s-\+,\]\[0123456789\*\]\[.\]\[0123456789\*\]\[L\]\{eEfgGoxX\} brightgreen keyword %\[0\s-\+,\]\[0123456789\*\]\[.\]\[0123456789\*\]\[hl\]\{diuxX\} brightgreen keyword %\[hl\]n brightgreen keyword %\[-\]\[0123456789\*\]\[.\]\[0123456789\*\]s brightgreen keyword %[*] brightgreen keyword %c brightgreen keyword %p brightgreen keyword \\\{0123\}\{01234567\}\{01234567\} brightgreen keyword brightgreen keyword \\' brightgreen keyword \\\{abtnvfr\} brightgreen ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Support Request: mcedit
Dear Sir, I'm using your product on a Linux server (distribution SuSE Linux Enterprise Server 11 Service Pack 3). The version I'm using is the latest version in the official repository : GNU Midnight Commander 4.6.2-pre1. The problem I have is when I'm modifying a text file using 'mcedit' and the connection goes down, the file will be closed. How can I restore the file? There is any temporary file that I can use to restore the missing part of the file? I've searched but I didn't find anything. If function is already developed in a later version, how can I update my version? Thanks for the support, Best Regards, Fabio Abbiati ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Support Request: mcedit
Dear Sir, I'm using your product on a Linux server (distribution SuSE Linux Enterprise Server 11 Service Pack 3). The version I'm using is the latest version in the official repository : GNU Midnight Commander 4.6.2-pre1. The problem I have is when I'm modifying a text file using 'mcedit' and the connection goes down, the file will be closed. How can I restore the file? There is any temporary file that I can use to restore the missing part of the file? I've searched but I didn't find anything. If function is already developed in a later version, how can I update my version? Thanks for the support, Best Regards, Fabio Abbiati ___ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
bugs on mcedit
The application, mcedit, would collapse and close when I choose thesyntax file and menu file on option in menu bar. The terminal displays asegment fault. Sorry, I am a Chinese and my English is not good. My OSis ubuntu12.04.___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
mcedit tags completion
Hello. I would like to ask whether it is possible in mcedit to make autocompletion use TAGS file? Now when I press M-Enter while cursor is on incomplete function name, mcedit suggests me to jump to function definition in another file, but when I press E-Tab, function's name can't be completed. If it is not possible, is there plans to introduce this functionality? And maybe it is better to show also function parameters, if they are present in the TAGS file just in case smbd forgot a function interface? Also is there a way to enable emacs-like or similar cursor movement commands in mcedit like in mc? Thanks in advance, Sergey Naumov. ___ mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
No spell check in 4.8.1 (mcedit)
Hi, I had some problmes with formatting in the 4.7.0.9 build so I added the nightly binary repo and got 4.8.1 which works great except for getting spell check to work. When I mark some text and do ispell from the drop down I get this error message: Cannot open file /home/user/share/mc/mcedit/macros.d/macro.1.sh/ No such file or directory (2). Could someone please help me getting spell check working? I'm running on a Linux Mint Debian system. -- //Christian ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
mcedit: Two spaces between words when formatting paragraph
Hi, I use mcedit for almost everything including composing e-mail. I have it set with typewriter wrapping which works well. But sometimes I need to use the 'Format Paragraph' (M-p) command. It works but several words get two spaces between them instead of one. What is the reason for that and is there a way I can prevent it? -- //Christian ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
word completion in mcedit
Hello. I would like to ask whether it is possible to use some key combination for word completion in mcedit instead of Esc + Tab? As to me, Ctrl + Space would be much more convinient to use. If there is no possibility for rebinding, is there a chance that Ctrl + Space will be added to newer versions of mc? Thanks in advance, Sergey Naumov. ___ mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
mcedit bug?
In mcedit function replace(F4) search string :^$ replacement string: check [x] regular expression and press [Enter], show window Confirm replace and press [Enter] results: STOP P.S. MC version 4.7.0.3 OS Gentoo Linux ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit bug?
On Wed, 30 Mar 2011 15:24:33 +0800 Dmitrij wrote: In mcedit function replace(F4) search string :^$ replacement string: check [x] regular expression and press [Enter], show window Confirm replace and press [Enter] results: STOP Yes, this is known bug: http://www.midnight-commander.org/ticket/1868 -- Andrew ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
mcedit tab color settings
Hi List, I'm using my own color scheme for Midnight Commander: http://monda.hu/blog/2009/05/11/kickass-black-midnight-commander-color-scheme/ Unfortunately tabs are visualized with blue background in mcedit and I couldn't find any info about what keyword should I use for defining its color. Please somebody help me. Thanks in advance. -- László Monda http://monda.hu ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit exit bug
Hello, Sorry, the mcedit exit bug was also a false alarm. I've configured mc to exit upon a _single_ Escape. But I got used to the double Escapes in the past too much, so I still do it occasionally. The 1st Escape exits mcedit, but the 2nd goes to the terminal. Sorry again G ___ mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
mcedit exit bug
Hello, I've found a small bug in standalone mcedit. It is my default editor, so for instance even git commit invokes it. After mcedit exits, it seems to leave some invisible character or escape sequence in my terminal, so the first character of my next command does not show up. Example: $ git commit# this invokes mcedit $ it push origin master # I actually typed git push... I have not seen any related ticket relevant for master. I'm using mc compiled from source: 2cfa57d Merge branch '2229_viewer_fast_move_up_down_wrapped' New Ticket? And I just remember, I also had a segfault while Find File, Search for content, at a gzipped manual page among the files. Best regards Gergely ___ mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit exit bug
Hello, I've just compiled and installed 58ea06d Merge branch '2417_edit_search_charset' I'm using gnome-terminal 2.30.2 (Ubuntu 10.04.1). Standalone mcedit still eats the 1st typed character after exiting. On the other hand, I can't reproduce the segfault in gzipped file while M-? Search for content. So I seem to be sending HOAX. :-) Best regards Gergely ___ mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit syntax highlighting
Hello Holger Herrlich, Am 2010-08-25 23:02:03, hacktest Du folgendes herunter: If you want to use a syntax highlighting not made available yet, you have to add an entry at the file 'Syntax' -- so copy to ~/.mc/cedit and do it. Thats not fully right, because If you create an Syntax in ~/.mc/cedit the global /usr/share/mc/syntax/Syntax is not more read... This is WHY I sayed, you have to copy the whole directory to your home. Or did I hit a forgotten bug under Woody, Sarge, Etch and Lenny? Note that mc (or maybe mcedit) has to be restarted to take effect Not right... Open a C Source Tree in the left panel and select a *.c file and hit F4 you see the file in the Editor highlighted... On the right panel and select the c.syntax and edit something, save and close it. Go back to the left panel and hit F4... Now it hast the changed syntax without leafing mc :-) Note: I am makeing SYNTAX files, VFS and menus since more then 8 years Thanks, Greetings and nice Day/Evening Michelle Konzack -- # Debian GNU/Linux Consultant ## Development of Intranet and Embedded Systems with Debian GNU/Linux itsyst...@tdnet France EURL itsyst...@tdnet UG (limited liability) Owner Michelle KonzackOwner Michelle Konzack Apt. 917 (homeoffice) 50, rue de Soultz Kinzigstraße 17 67100 Strasbourg/France 77694 Kehl/Germany Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil Tel: +33-9-52705884 fix http://www.itsystems.tamay-dogan.net/ http://www.flexray4linux.org/ http://www.debian.tamay-dogan.net/ http://www.can4linux.org/ Jabber linux4miche...@jabber.ccc.de ICQ#328449886 Linux-User #280138 with the Linux Counter, http://counter.li.org/ signature.pgp Description: Digital signature ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit syntax highlighting
On Sat, 21 Aug 2010, Michelle Konzack wrote: To: mc@gnome.org From: Michelle Konzack linux4miche...@tamay-dogan.net Subject: Re: mcedit syntax highlighting Hello Stanisław Findeisen, Am 2010-08-21 14:56:21, hacktest Du folgendes herunter: On 2010-08-21 03:10, Michelle Konzack wrote: He can put the files under ~/.mc/cedit/ :-D Thanks! It works! What a cool files! :-) In the time when I had found out it, there was not a singel indice, that you can do that... I have ried it out and it worked! But there is a problem with it: If you have /usr/share/mc/syntax/Syntax and ~/.mc/cedit/Syntax the later one takes precedence and if you have only C Source Code defined, any other Syntax files from /usr/share/mc/syntax/ will be ignored. What about copying ALL the mc syntax files to the user's ~/.mc/cedit/Syntax directory? Does that work? FOR THE DEVELOPERS: It would be an advantage, if the developers of MC could do a merge of the two directories with precedence on ~/.mc/cedit/Syntax and if a Syntax file is not found, MC looks into /usr/share/mc/syntax/ Thanks, Greetings and nice Day/Evening Michelle Konzack That makes perfect sense to me Michelle. So each user can have their own custom versions of the mc syntax files. As they are in the user's home directory, they would not get overwritten when there is an update to mc. Kind Regards, Keith Roberts - Websites: http://www.php-debuggers.net http://www.karsites.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit syntax highlighting
Hello Keith Roberts, Am 2010-08-21 19:54:36, hacktest Du folgendes herunter: What about copying ALL the mc syntax files to the user's ~/.mc/cedit/Syntax directory? Does that work? This is what I have done. and it works flawless, but if you have a major update of mc which adds new Syntaxfiles, you have to care about it. That makes perfect sense to me Michelle. So each user can have their own custom versions of the mc syntax files. As they are in the user's home directory, they would not get overwritten when there is an update to mc. Exactly. However, I do not recommend copying the files (at the very first startup of MC) to the users ~/.mc/cedit/ since it could lead to problems with updated exspecialy with less experienced users. Thanks, Greetings and nice Day/Evening Michelle Konzack -- # Debian GNU/Linux Consultant ## Development of Intranet and Embedded Systems with Debian GNU/Linux itsyst...@tdnet France EURL itsyst...@tdnet UG (limited liability) Owner Michelle KonzackOwner Michelle Konzack Apt. 917 (homeoffice) 50, rue de Soultz Kinzigstraße 17 67100 Strasbourg/France 77694 Kehl/Germany Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil Tel: +33-9-52705884 fix http://www.itsystems.tamay-dogan.net/ http://www.flexray4linux.org/ http://www.debian.tamay-dogan.net/ http://www.can4linux.org/ Jabber linux4miche...@jabber.ccc.de ICQ#328449886 Linux-User #280138 with the Linux Counter, http://counter.li.org/ signature.pgp Description: Digital signature ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
mcedit syntax highlighting
Hi I have a horrible syntax highlighting when editing C files with mcedit. It hurts my eyes. How can this be fixed? For instance I'd prefer #includes and #defines to be light green rather than red. Thanks! STF http://eisenbits.homelinux.net/~stf/ OpenPGP: DFD9 0146 3794 9CF6 17EA D63F DBF5 8AA8 3B31 FE8A inline: mcedit.png___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit syntax highlighting
Hello Keith Roberts, Am 2010-08-20 21:16:11, hacktest Du folgendes herunter: Well you don't say which OS platform you are using. On Fedora 12 mcedit's syntax files are under, /usr/share/mc/syntax/ If you edit your syntax files, be sure to make backup copies somewhere. Because when mc is updated, it WILL overwrite all you edits to your mc syntax files. For what? He can put the files under ~/.mc/cedit/ :-D Thanks, Greetings and nice Day/Evening Michelle Konzack -- # Debian GNU/Linux Consultant ## Development of Intranet and Embedded Systems with Debian GNU/Linux itsyst...@tdnet France EURL itsyst...@tdnet UG (limited liability) Owner Michelle KonzackOwner Michelle Konzack Apt. 917 (homeoffice) 50, rue de Soultz Kinzigstraße 17 67100 Strasbourg/France 77694 Kehl/Germany Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil Tel: +33-9-52705884 fix http://www.itsystems.tamay-dogan.net/ http://www.flexray4linux.org/ http://www.debian.tamay-dogan.net/ http://www.can4linux.org/ Jabber linux4miche...@jabber.ccc.de ICQ#328449886 Linux-User #280138 with the Linux Counter, http://counter.li.org/ signature.pgp Description: Digital signature ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: Change in mcedit exit dialog
On Sun, Jul 11, 2010 at 02:41:40AM +0100, Norbert Nemec wrote: I just installed 4.7.3 and was very surprised by the change in the exit dialog of mcedit. http://www.midnight-commander.org/ticket/2265 ___ mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Change in mcedit exit dialog
Hi there, I just installed 4.7.3 and was very surprised by the change in the exit dialog of mcedit. After years of using mcedit, I do not even think about the key sequence for saving and quitting: [F10],[right],[return] It used to be that the exit dialog would have three buttons [cancel] [save] [discard] Now suddenly, the order has changed to [save] [discard] [cancel] So now the key sequence that is burned into my brain from years of using mc results in [discard] rather than [save] as it used to. I have been trapped by this at least ten times within a few hours. First editing a file, then intending to save the changes but instead discard them. Could the exit dialog please be changed back to the original order? It may not be perfect and there may be good reasons to change it, but simply swapping the buttons in such a dangerous way will certainly annoy any long-time user of midnight commander. Greetings, Norbert Nemec ___ mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[feature request] mcedit: editing several files at once
Hi, After a bit of search, I've been unable to find if that was ever asked. Do you plan to extend mcedit so that editing several files at once become possible ? (with some kind of a buffer à la vi or something). It would be nice to have, imho. Keep up the good work, Regards, -- Laurent Wandrebeck GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D 2A62 54E6 EF2C D17C F64C pgpqkYTdB8iAN.pgp Description: PGP signature ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: [feature request] mcedit: editing several files at once
On Tue, 2010-05-11 at 15:23 +0200, Laurent Wandrebeck wrote: After a bit of search, I've been unable to find if that was ever asked. Check out the Trac, I guess there was a request for screen multiplexing. However, personally, I don't see a room for such feature when there's screen and tmux already. -- Sincerely yours, Yury V. Zaytsev ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
On unexpected case sensitivity in regex searches in mcedit
This still occurs in mc 4.7.0.4. Sigh... Regexes within brackets '[]' appear to be the ones affected. Reynir Heiðberg Stefánssonreyni...@mi.is ___ mc mailing list http://mail.gnome.org/mailman/listinfo/mc
mcedit
I use mcedit constantly, running it on an OS X 10.5.8 terminal to numerous remote redhat 9 linux machines from within mc, and on occasion invoked as mcedit (which I presume, as per the docs, is just mc -e.). On occasion, I run into a file with ^M at the end of a line in MCEDIT. I can delete these one at a time if I position the cursor right on them. I have tried many things to attempt and use the F4 global search and replace, but nothing seems to work in the first field, the search field. I would leave the replace field empty, because I want them gone. Regular expressions - no. ^M, no. The format string replace... I don't even understand HOW you would use that to find a control character. %015, no. \015, no. \r, no. %13, no. %0D, no. 0x0D, no. [^M], no. There's a [^] field at the end of the line, but I can't seem to get to it with tab, and the mouse flat out does nothing in an mcedit pane. I've been to the documentation (hah!) and I've searched using Google. Nothing. I know I can use sed, etc., to do this, but I don't always have execute privileges in the directories I'm working in, because I'm in remotely via SSH in one pane - the filesystem is remote. Could someone take pity on me and tell me how it's supposed to work? Thanks. ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit
On Wed, 10 Mar 2010 08:12:08 -0700 Ben wrote: Regular expressions - no. ^M, no. The format string replace... I don't even understand HOW you would use that to find a control character. %015, no. \015, no. \r, no. %13, no. %0D, no. 0x0D, no. [^M], no. Strange. Enter search string: \r Enter replacement string: empty (*) Regular expression Works fine for me. mc-4.7.1 -- Andrew ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit
I use mcedit constantly, running it on an OS X 10.5.8 terminal to numerous remote redhat 9 linux machines from within mc, and on occasion invoked as mcedit (which I presume, as per the docs, is just mc -e.). On occasion, I run into a file with ^M at the end of a line in MCEDIT. I can delete these one at a time if I position the cursor right on them. I have tried many things to attempt and use the F4 global search and replace, but nothing seems to work in the first field, the search field. I would leave the replace field empty, because I want them gone. Regular expressions - no. ^M, no. The format string replace... I don't even understand HOW you would use that to find a control character. %015, no. \015, no. \r, no. %13, no. %0D, no. 0x0D, no. [^M], no. There's a [^] field at the end of the line, but I can't seem to get to it with tab, and the mouse flat out does nothing in an mcedit pane. I've been to the documentation (hah!) and I've searched using Google. Nothing. I know I can use sed, etc., to do this, but I don't always have execute privileges in the directories I'm working in, because I'm in remotely via SSH in one pane - the filesystem is remote. Could someone take pity on me and tell me how it's supposed to work? Thanks. ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit
Hello Ben, On Wed, 10 Mar 2010 09:01:36 -0700 Ben 2blkb...@nemontel.net wrote: I use mcedit constantly, running it on an OS X 10.5.8 terminal to numerous remote redhat 9 linux machines from within mc, and on occasion invoked as mcedit (which I presume, as per the docs, is just mc -e.). On occasion, I run into a file with ^M at the end of a line in MCEDIT. I can delete these one at a time if I position the cursor right on them. I have tried many things to attempt and use the F4 global search and replace, but nothing seems to work in the first field, the search field. I would leave the replace field empty, because I want them gone. Regular expressions - no. ^M, no. The format string replace... I don't even understand HOW you would use that to find a control character. %015, no. \015, no. \r, no. %13, no. %0D, no. 0x0D, no. [^M], no. There's a [^] field at the end of the line, but I can't seem to get to it with tab, and the mouse flat out does nothing in an mcedit pane. I've been to the documentation (hah!) and I've searched using Google. Nothing. I know I can use sed, etc., to do this, but I don't always have execute privileges in the directories I'm working in, because I'm in remotely via SSH in one pane - the filesystem is remote. Could someone take pity on me and tell me how it's supposed to work? You can use \n and make sure you check the regular expression widget. At least it works w/ 4.7.1, even if mcedit completely freezes when you choose All in the confirm replace dialog. Regards, -- wwp signature.asc Description: PGP signature ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit
On Wed, 2010-03-10 at 10:34 -0700, Ben wrote: Is there truly no way to search for ^M or other embedded control characters? ^M are not the embedded control characters. It's just the way mcedit represents \r's (carriage return character). So if you run dos2unix on the file or search and replace \r's (ASCII 13) with it should do the trick. I guess there've been numerous requests to add an option to not show \r's in the editor, however I don't remember whether they made their way to the Trac or not. Your best bet would be to search the Trac and 1) If such a ticket exists, vote for it 2) If it does not, then create it. -- Sincerely yours, Yury V. Zaytsev ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit
On Wed, 10 Mar 2010, Yury V. Zaytsev wrote: On Wed, 2010-03-10 at 10:34 -0700, Ben wrote: Is there truly no way to search for ^M or other embedded control characters? ^M are not the embedded control characters. It's just the way mcedit represents \r's (carriage return character). So if you run dos2unix on the file or search and replace \r's (ASCII 13) with it should do the trick. I guess there've been numerous requests to add an option to not show \r's in the editor, however I don't remember whether they made their way to the Trac or not. Your best bet would be to search the Trac and 1) If such a ticket exists, vote for it 2) If it does not, then create it. OK, here is a vote. If those things are in the file, I prefer to see them, thanks. There are occasions when those DOS control characters can really get in the way, and to have a situation where the problem is hidden so that nobody can see exactly what the problem is makes the problem even worse. For example, sometimes one gets some C code from some other place, and somewhere along the way those ^M characters have been stuck on every line, when it is not good at all to have them lurking there. In such situations, the extra control characters are then removable by running the file through dos2unix, for example, and one had better do that. At the same time, I can see that someone else has a different problem and needs not to see them. I can understand his problem, and I sympathize. But please do not try to solve his problem by screwing things up for others. Try to think of another way around his problem, instead. Theodore Kilgore ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit
On Wed, 2010-03-10 at 16:21 -0600, Theodore Kilgore wrote: At the same time, I can see that someone else has a different problem and needs not to see them. I can understand his problem, and I sympathize. But please do not try to solve his problem by screwing things up for others. Try to think of another way around his problem, instead. I didn't suggest to screw things up for anyone. There've been some discussions on adding an option which would be disabled by default to not to show them, but I don't remember whether they made it to the Trac or not... -- Sincerely yours, Yury V. Zaytsev ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: mcedit
On Wed, 10 Mar 2010, Yury V. Zaytsev wrote: On Wed, 2010-03-10 at 16:21 -0600, Theodore Kilgore wrote: At the same time, I can see that someone else has a different problem and needs not to see them. I can understand his problem, and I sympathize. But please do not try to solve his problem by screwing things up for others. Try to think of another way around his problem, instead. I didn't suggest to screw things up for anyone. There've been some discussions on adding an option which would be disabled by default to not to show them, but I don't remember whether they made it to the Trac or not... Ah. Yes, if an option were available which can work that way, it would take care of the problem. Theodore Kilgore ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
[Fwd: [Pkg-mc-devel] Bug#570502: mcedit: adding extra spaces when pasting a text preceded by spaces]
Hi guys! Could you please have a look? mc 4.7.0.1 / autoindent on enter is on. Is this a bug or not? -- Sincerely yours, Yury V. Zaytsev Forwarded Message When pasting a text preceded by spaces, mcedit puts extra spaces/tabs before each line. It is very inconvenient and I have used vi or nano when I need paste a extra text. An example. Original text: -x-x-x- text test 1 text test 2 text test 3 text test 4 text test 5 text test 6 text test 7 text test 8 text test 9 -x-x-x- Pasted text into mcedit (between -x-x-x-): -x-x-x- text test 1 text test 2 text test 3 text test 4 text test 5 text test 6 text test 7 text test 8 text test 9 -x-x-x- Please, also note the spaces added in the last four lines. Thanks, Eriberto - Brazil ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: replace mcedit with emacsclient without chaning $EDITOR
On Tue, Feb 09, 2010 at 09:13:00AM +0300, Andrew Borodin wrote: On Mon, 8 Feb 2010 19:38:15 -0500 Haines Brown KB1GRM ET1 wrote: ... Please write exactly what you did. /usr/share/mc/bin/mc-wrapper.sh must be run directly or via some wrapper like /etc/bashrc.d/mc.sh. In mc-wrapper.sh, I added EDITOR=/usr/bin/vim line before /usr/bin/mc -P $MC_PWD_FILE $@ then started mc and unchecked the 'use internal edIt' option. If I press F4 key, the selected file is opened in vim. In MC Configuration Options, I have unchecked Use intenal edit and Use internal view. I assume this is why nano normally comes up as editor rather than mcedit. In /usr/share/mc/bin/mc-wrapper.sh I followed your advice and moved the EDITOR=/usr/bin/emacsclient line to before the /usr/bin/mc -P $MC_PWD_FILE $@ line. Nano still comes up as editor. I tried using EDITOR=/usr/bin/emacs instead, but had same result. This is all I did. I'm unclear how mc-wrapper.sh is run directly, for it is not an executable on my machine and belongs to root, and I'm assuming you are not suggesting a change in those default parameters. My mc.sh is in the same directory as mc-wrapper.sh, and only provides an alias for mc: alias mc='. /usr/share/mc/bin/mc-wrapper.sh' The space between . and / puzzles me. Also, emacsclient command, unlike vim, needs an argument. Haines ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: replace mcedit with emacsclient without chaning $EDITOR
On Mon, Feb 08, 2010 at 10:22:03AM +0300, Andrew Borodin wrote: On Sun, 7 Feb 2010 12:10:17 -0500 Haines Brown KB1GRM ET1 wrote: The way to do this typically seems to change the value of the variable $EDITOR, but I don't want to do that system-wide, but only for mc, so that F4 brings up emacsclient to edit files, and nano is the default editor system-wide. How would I manage to do that? Unable to find help. MC contains two wrappers for bash: /etc/bashrc.d/mc.sh and /usr/lib/mc/mc-wrapper.sh. The same wrappers are exist for csh. But in your MC build that scripts can be located in different places. You can redefine the EDITOR variable in one of them. Andrew, Tbanks, but apparently I missed something. I have a /usr/share/mc/bin/mc-wrapper.sh. In it I append the line: EDITOR=/usr/bin/emacsclient The mc editor, however, remains nano. The line is ignored. Haines ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: replace mcedit with emacsclient without chaning $EDITOR
On Mon, 8 Feb 2010 19:38:15 -0500 Haines Brown KB1GRM ET1 wrote: Tbanks, but apparently I missed something. I have a /usr/share/mc/bin/mc-wrapper.sh. In it I append the line: EDITOR=/usr/bin/emacsclient The mc editor, however, remains nano. The line is ignored. Please write exactly what you did. /usr/share/mc/bin/mc-wrapper.sh must be run directly or via some wrapper like /etc/bashrc.d/mc.sh. In mc-wrapper.sh, I added EDITOR=/usr/bin/vim line before /usr/bin/mc -P $MC_PWD_FILE $@ then started mc and unchecked the 'use internal edIt' option. If I press F4 key, the selected file is opened in vim. -- Andrew ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
replace mcedit with emacsclient without chaning $EDITOR
With advancing age, keeping competitive keybindings straight is more of a challenge, and so I'd like to replace mcedit (as much as I like it) with emacsclient (which exsts on my machine). The way to do this typically seems to change the value of the variable $EDITOR, but I don't want to do that system-wide, but only for mc, so that F4 brings up emacsclient to edit files, and nano is the default editor system-wide. How would I manage to do that? Unable to find help. Haines Brown ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: replace mcedit with emacsclient without chaning $EDITOR
On Sun, 7 Feb 2010 12:10:17 -0500 Haines Brown KB1GRM ET1 wrote: The way to do this typically seems to change the value of the variable $EDITOR, but I don't want to do that system-wide, but only for mc, so that F4 brings up emacsclient to edit files, and nano is the default editor system-wide. How would I manage to do that? Unable to find help. MC contains two wrappers for bash: /etc/bashrc.d/mc.sh and /usr/lib/mc/mc-wrapper.sh. The same wrappers are exist for csh. But in your MC build that scripts can be located in different places. You can redefine the EDITOR variable in one of them. -- Andrew ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
mcedit and interrupted ssh session
Hello, I was connected with putty to a linux host and inside it editing a file with 'mcedit -d /path/to/filename'. The ssh connection broke. The mcedit process is still running on the linux host. Is there any way to recover the text from that mcedit process? If so, what are the steps that should be followed? mc version: 4.6.2~git20080311-4, on debian lenny i686 Many thanks in advance! Please include me in CC as I'm not subscribed on the list. Costin ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
[Midnight Commander] #267: C code navigation in mcedit
#267: C code navigation in mcedit -+-- Reporter: angel_il | Owner: Type: enhancement | Status: new Priority: minor| Milestone: 4.7 Component: mcedit | Version: 4.6.2 Keywords: |Blocking: Blockedby: | -+-- It would be good to have possibility in the mcedit to navigate to function definition. Using for this purpose the utility ctags and parse tags file in the current directory. -- Ticket URL: www.midnight-commander.org/ticket/267 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #267: C-code navigation in mcedit (was: C code navigation in mcedit)
#267: C-code navigation in mcedit --+- Reporter: angel_il | Owner: Type: enhancement | Status: new Priority: minor| Milestone: 4.7 Component: mcedit | Version: 4.6.2 Resolution: |Keywords: Blocking: | Blockedby: --+- -- Ticket URL: www.midnight-commander.org/ticket/267#comment:1 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
mcedit patches for ticket#113
I had previously tackled Savannah bug id#13146 (copied to trac as ticket #113) and added a slew of patches for it to the opensuse mc package. I now rebased them for the new git repo and published it at git://dev.medozas.de/mc master with commits ebbefa3e(^)..18408124: build: remove auto-generated m4 files mcedit: move syntax highlight options into their own dialog mcedit: implement EOL mark mcedit: fix whitespace styling mcedit: provide alternate tab style mcedit: provide alternate space style The UTF-8 branch is a hard requirement, but IMHO, the utf8 stuff is more than ready, as it has been in use for a long time in the distro already. Please review, comment, and perhaps merge. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #148: Re: mcedit - fancy tab handling
#148: Re: mcedit - fancy tab handling ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: defect| Status: accepted Priority: major | Milestone: 4.7 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: review vote-metux Blocking:| Blockedby: ---+ Changes (by metux): * keywords: review = review vote-metux Old description: Am Montag 05 Januar 2009 21:40:43 schrieb Janek Kozicki: I'm attaching here the patch which is in use inside debian for a long time to add a shortcut in order to turn this behaviour off and on. Please comment on this patch. Should this also applied against mc-4.6 (which should only hold bugfixes) or should this go only into a coming 4.7 release? Greetings Winnie New description: Am Montag 05 Januar 2009 21:40:43 schrieb Janek Kozicki: I'm attaching here the patch which is in use inside debian for a long time to add a shortcut in order to turn this behaviour off and on. Please comment on this patch. Should this also applied against mc-4.6 (which should only hold bugfixes) or should this go only into a coming 4.7 release? -- branch:148_fancy_tab_handling changeset:c3a1d292fd90ee05dbe3227f5b8428961431e434 -- -- Ticket URL: www.midnight-commander.org/ticket/148#comment:4 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #148: Re: mcedit - fancy tab handling
#148: Re: mcedit - fancy tab handling ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: defect| Status: accepted Priority: major | Milestone: 4.7 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: vote-metux vote-slavazanko approved Blocking:| Blockedby: ---+ Changes (by slavazanko): * keywords: review vote-metux = vote-metux vote-slavazanko approved -- Ticket URL: www.midnight-commander.org/ticket/148#comment:5 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #148: Re: mcedit - fancy tab handling
#148: Re: mcedit - fancy tab handling ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: defect| Status: testing Priority: major | Milestone: 4.7 Component: mc-core | Version: 4.6.1 Resolution: fixed |Keywords: vote-metux vote-slavazanko approved committed-master Blocking:| Blockedby: ---+ Changes (by winnie): * keywords: vote-metux vote-slavazanko approved = vote-metux vote- slavazanko approved committed-master * status: accepted = testing * resolution: = fixed -- Ticket URL: www.midnight-commander.org/ticket/148#comment:6 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #148: Re: mcedit - fancy tab handling
#148: Re: mcedit - fancy tab handling ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: defect| Status: closed Priority: major | Milestone: 4.7 Component: mc-core | Version: 4.6.1 Resolution: fixed |Keywords: vote-metux vote-slavazanko approved committed-master Blocking:| Blockedby: ---+ Changes (by winnie): * status: testing = closed -- Ticket URL: www.midnight-commander.org/ticket/148#comment:7 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Regexp problems in mcedit?
Is it just me, or does F4 (Search/Replace) with regular expressions sometimes fail in mysterious ways for others as well? Reynir H. Stefánsson (reyni...@mi.is) -- Would compiler technology have advanced as greatly as it has without C? Would it have had to? ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: [Midnight Commander] #148: Re: mcedit - fancy tab handling
#148: Re: mcedit - fancy tab handling ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: defect| Status: accepted Priority: major | Milestone: 4.7 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: review Blocking:| Blockedby: ---+ Changes (by winnie): * owner: = winnie * status: new = accepted Comment: Setting me as owner in order to get this as fast as possible to master. -- Ticket URL: www.midnight-commander.org/ticket/148#comment:3 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[Midnight Commander] #148: Re: mcedit - fancy tab handling
#148: Re: mcedit - fancy tab handling --+- Reporter: Patrick Winnertz win...@debian.org | Owner: Type: defect| Status: new Priority: major | Milestone: 4.7 Component: mc-core | Version: 4.6.1 Keywords:|Blocking: Blockedby:| --+- Am Montag 05 Januar 2009 21:40:43 schrieb Janek Kozicki: I'm attaching here the patch which is in use inside debian for a long time to add a shortcut in order to turn this behaviour off and on. Please comment on this patch. Should this also applied against mc-4.6 (which should only hold bugfixes) or should this go only into a coming 4.7 release? Greetings Winnie -- Ticket URL: www.midnight-commander.org/ticket/148 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #148: Re: mcedit - fancy tab handling
#148: Re: mcedit - fancy tab handling ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: Type: defect| Status: new Priority: major | Milestone: 4.7 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: review Blocking:| Blockedby: ---+ Changes (by metux): * keywords: = review Old description: Am Montag 05 Januar 2009 21:40:43 schrieb Janek Kozicki: I'm attaching here the patch which is in use inside debian for a long time to add a shortcut in order to turn this behaviour off and on. Please comment on this patch. Should this also applied against mc-4.6 (which should only hold bugfixes) or should this go only into a coming 4.7 release? Greetings Winnie New description: Am Montag 05 Januar 2009 21:40:43 schrieb Janek Kozicki: I'm attaching here the patch which is in use inside debian for a long time to add a shortcut in order to turn this behaviour off and on. Please comment on this patch. Should this also applied against mc-4.6 (which should only hold bugfixes) or should this go only into a coming 4.7 release? Greetings Winnie -- -- Ticket URL: www.midnight-commander.org/ticket/148#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit - fancy tab handling
Enrico Weigelt said: (by the date of Mon, 5 Jan 2009 19:22:25 +0100) Hi folks, I've just seen that current mcedit (from git tree) has some fancy tab handling (shows -- symbols). When had this been introduced ? I noticed this after upgrading debian etch to lenny. I like it, but sometimes it's inconvenient when I want to copy/paste with mouse. (using shift-mouseclicks) The best if there's a way to turn it on/off. And if it's somewhere easily accessible with menu/shortcuts. -- Janek Kozicki | ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit - fancy tab handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Janek Kozicki wrote: Enrico Weigelt said: (by the date of Mon, 5 Jan 2009 19:22:25 +0100) Hi folks, I've just seen that current mcedit (from git tree) has some fancy tab handling (shows -- symbols). When had this been introduced ? I noticed this after upgrading debian etch to lenny. I like it, but sometimes it's inconvenient when I want to copy/paste with mouse. (using shift-mouseclicks) The best if there's a way to turn it on/off. And if it's somewhere easily accessible with menu/shortcuts. mc-ru-fork have this feature. And toggle space/tabs view via CTRL+v hotkey in editor... I will make valid patch from mc-ru-fork for 'master' at near time. WBR, Slavaz. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklicpsACgkQb3oGR6aVLprpGACfXjpxS3FTwJ9Fl1e293TPllZo G2kAnjSwU7KODO1ZF+o6bU8nCu6OmtpQ =WpmA -END PGP SIGNATURE- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[patch] Invoking mcedit with filename:lineno
Hi, many programs output warnings and errors in the format filename:lineno[:]. The attached patch allows users to just copy and paste these locations and invoke mcedit with them. For example: $ mcedit main.c:2000 The patch maintains the usual behavior as much as possible. That is, the new format is only used when the file main.c:2000 doesn't exist, but main.c exists. Opinions? Roland Index: doc/mcedit.1.in === RCS file: /cvsroot/mc/mc/doc/mcedit.1.in,v retrieving revision 1.22 diff -u -p -r1.22 mcedit.1.in --- doc/mcedit.1.in 24 Sep 2007 12:50:37 - 1.22 +++ doc/mcedit.1.in 9 Dec 2008 12:44:12 - @@ -3,7 +3,10 @@ mcedit \- Internal file editor of GNU Midnight Commander. .SH USAGE .B mcedit -[\-bcCdfhstVx?] [+number] file +[\-bcCdfhstVx?] [+lineno] file +.PP +.B mcedit +[\-bcCdfhstVx?] file:lineno[:] .SH DESCRIPTION .LP mcedit is a link to @@ -18,8 +21,8 @@ version of \- standalone editor for X Window System. .SH OPTIONS .TP -.I +number -Go to the line specified by number (do not put a space between the +.I +lineno +Go to the line specified by number (do not put a space between the .I + sign and the number). .TP Index: src/main.c === RCS file: /cvsroot/mc/mc/src/main.c,v retrieving revision 1.370 diff -u -p -r1.370 main.c --- src/main.c 25 Sep 2007 15:33:37 - 1.370 +++ src/main.c 9 Dec 2008 12:44:12 - @@ -2055,17 +2055,41 @@ handle_args (int argc, char *argv[]) if (!STRNCOMP (base, mce, 3) || !STRCOMP (base, vi)) { edit_one_file = ; if (tmp) { - if (*tmp == '+' isdigit ((unsigned char) tmp[1])) { - int start_line = atoi (tmp); - if (start_line 0) { - char *file = poptGetArg (ctx); - if (file) { - tmp = file; - edit_one_file_start_line = start_line; + /* + * Check for filename:lineno, followed by an optional colon. + * This format is used by many programs (especially compilers) + * in error messages and warnings. It is supported so that + * users can quickly copy and paste file locations. + */ + char *end = tmp + strlen (tmp), *p = end; + if (p tmp p[-1] == ':') + p--; + while (p tmp isdigit ((unsigned char) p[-1])) + p--; + if (tmp p p end p[-1] == ':') { + struct stat st; + gchar *fname = g_strndup (tmp, p - 1 - tmp); + if (mc_stat (tmp, st) == -1 mc_stat (fname, st) != -1) { + edit_one_file = fname; + edit_one_file_start_line = atoi (p); + } else { + g_free (fname); + goto try_plus_filename; + } + } else { + try_plus_filename: + if (*tmp == '+' isdigit ((unsigned char) tmp[1])) { + int start_line = atoi (tmp); + if (start_line 0) { + char *file = poptGetArg (ctx); + if (file) { + tmp = file; + edit_one_file_start_line = start_line; + } } } + edit_one_file = g_strdup (tmp); } - edit_one_file = g_strdup (tmp); } } else if (!STRNCOMP (base, mcv, 3) || !STRCOMP (base, view)) { if (tmp) ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[bug #21873] Conflicting Alt+O keyboard shortcut in mcedit
Follow-up Comment #1, bug #21873 (project mc): Well this has been fixed in the latest version of mcedit, but I can't see how to close off this bug... ___ Reply to this item at: http://savannah.gnu.org/bugs/?21873 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
execute n times macro on mcedit - faster version
modify to execute n times a macro - faster version: File: edit.c the changes are in bold: static void edit_execute_macro (WEdit *edit, struct macro macro[], int n, long num); . void edit_execute_cmd (WEdit *edit, int command, int char_for_insertion) { /* CK_Pipe_Block */ if ((command / 1000) == 1) /* a shell command */ edit_block_process_cmd (edit, shell_cmd[command - 1000], 1); if (command CK_Macro (0) command = CK_Last_Macro) { /* a macro command */ struct macro m[MAX_MACRO_LENGTH]; int nm; if (edit_load_macro_cmd (edit, m, nm, command - 2000)) { /* inizio modifica per eseguire la macro tante volte */ char *NRmacro; static long line = 0; char *error; long NREmacro = 0; long l; char s[32]; NRmacro = input_dialog (_( Execute Macro ), _( How many times: ), NREmacro ? s : ); if (!NRmacro) goto finc; if (!*NRmacro) { g_free (NRmacro); goto finc; } l = strtol (NRmacro, error, 0); if (*error) { g_free (NRmacro); goto finc; } NREmacro = l; edit_execute_macro (edit, m, nm, NREmacro); } } finc: .. static void edit_execute_macro (WEdit *edit, struct macro macro[], int n, long num) { long j; /* int i = 0; */ if (edit-macro_depth++ 256) { edit_error_dialog (_(Error), _(Macro recursion is too deep)); edit-macro_depth--; return; } edit-force |= REDRAW_PAGE; for (j = 1; j = num; j++) { int i = 0; for (; i n; i++) { edit_execute_cmd (edit, macro[i].command, macro[i].ch); } } edit_update_screen (edit); edit-macro_depth--; } Dario Benenati Uno Sistemi s.r.l. Via Giovanni Verga, 7 62010 Morrovalle Scalo (MC) - Italy Tel. +39 0733 865264 Fax +39 0733 865791 Nota confidenziale: il presente messaggio e/o eventuali allegati è rivolto unicamente all'attenzione del destinatario ed il contenuto potrebbe avere carattere riservato. Se il presente messaggio e/o eventuali allegati Le fosse pervenuto per errore Vorrà provvedere alla sua distruzione e Le saremmo grati se ce ne comunicasse via e-mail l'errata ricezione all'indirizzo [EMAIL PROTECTED] Il contenuto del presente messaggio e/o eventuali allegati non impegnano Uno Sistemi s.r.l. nei confronti del destinatario o di terzi. Uno Sistemi s.r.l. non si assume alcuna responsabilità per eventuali intercettazioni, modifiche o danneggiamenti del presente messaggio e-mail e/o eventuali allegati. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
execute n times macro on mcedit
I have modify edit.c to execute n times a macro. This is the modify code in void edit_execute_cmd ... : if (command CK_Macro (0) command = CK_Last_Macro) { /* a macro command */ struct macro m[MAX_MACRO_LENGTH]; int nm; if (edit_load_macro_cmd (edit, m, nm, command - 2000)) { /* # BEGIN MODIFY ## */ char *NRmacro; static long line = 0; /* line as typed, saved as default */ char *error; long NREmacro = 0; long l; char s[32]; NRmacro = input_dialog (_( Macro execute), _( How many times: ), NREmacro ? s : ); if (!NRmacro) goto finc; if (!*NRmacro) { g_free (NRmacro); goto finc; } l = strtol (NRmacro, error, 0); if (*error) { g_free (NRmacro); goto finc; } NREmacro = l; int j; for (j = 1; j = NREmacro; j++) { edit_execute_macro (edit, m, nm); } finc: /* # END MODIFY */ } } Dario Benenati Uno Sistemi s.r.l. Via Giovanni Verga, 7 62010 Morrovalle Scalo (MC) - Italy Tel. +39 0733 865264 Fax +39 0733 865791 Nota confidenziale: il presente messaggio e/o eventuali allegati è rivolto unicamente all'attenzione del destinatario ed il contenuto potrebbe avere carattere riservato. Se il presente messaggio e/o eventuali allegati Le fosse pervenuto per errore Vorrà provvedere alla sua distruzione e Le saremmo grati se ce ne comunicasse via e-mail l'errata ricezione all'indirizzo [EMAIL PROTECTED] Il contenuto del presente messaggio e/o eventuali allegati non impegnano Uno Sistemi s.r.l. nei confronti del destinatario o di terzi. Uno Sistemi s.r.l. non si assume alcuna responsabilità per eventuali intercettazioni, modifiche o danneggiamenti del presente messaggio e-mail e/o eventuali allegati. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Bug in mcedit - syntax highlighting
Hello and at first thanks for mc, it's a great convenience! I have a problem with syntax highlighting in mcedit from time to time, here is an example: -- code snippet #!/bin/bash ... # $sd/mbrola -e -t 1.2 -f 0.80 $sd/de2/de2 - $wd/my.au maxVol=$(/usr/bin/mpc volume | /usr/bin/awk '{print substr($2,1,2)}') ALL LINES FOLLOWING AFTER THIS LINE ARE IN GREEN COLOR, NO HIGHLIGHTING ANYMORE for ((vol=maxVol; vol30; vol-=2)) do ... I watch this effect for over a year now so i decided to write this hint today. Thanks for your endevour in advance, greetings, Manfred. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit annoying syntax highlight changes
On Sat, Jun 28, 2008 at 02:33:59PM +0200, Jan Engelhardt wrote: starting with mc 4.6.2, there have been changes to the syntax highlighting, specifically displaying whitespace. http://savannah.gnu.org/bugs/?func=detailitemitem_id=13146 -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Confusion, chaos, panic - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
mcedit annoying syntax highlight changes
Hi, starting with mc 4.6.2, there have been changes to the syntax highlighting, specifically displaying whitespace. int main(void) { --if (this) { that; --} } While I welcome this, I sometimes prefer to have it turned off[1]. Looking at the source code, I see no tunable to control displaying whitespace, nor a color setting to make it at least the same as the background color. [1] http://tinyurl.com/4e7su9 edit/editdraw.c line 118: int visible_tabs = 1, visible_tws = 1; all other uses of these variables are read-only. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: question about mcedit
Hi Cris, please can you use a REAL tool to split the Digest into singel messages and reply correctly? Messages like yours are annoying! Also do not produce TOFU (fullquot) And of course, the image was gone to the list since I have replied to him. Thanks, Greetings and nice Day Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: question about mcedit
Hello Raimundas, Am 2008-05-12 14:56:48, schrieb Raimundas Kan??auskas: hi, i using mcedit for editing php files. i cant find how to turnoff paragraph symbols (right side in attached file). please write my how to turn off it. thank you. END OF REPLIED MESSAGE I see not paragraph symbols (the doubled S) or do you mine the Dollar $ sign which show a variable? Thanks, Greetings and nice Day Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
mcedit screw up mutt index
Hello Pavel, Do you have gotten the message from the Debian Maintainer? The Bug# 473980 and there is a setting in mc which screw up the index-view of mutt, since if I remove the ~/.mc/ directory and start mutt and then write a message with it, it does not screw up the linedrawings in mutt but if I remove the newly created ~/.mc/ directory and copy the OLD ~/.mc/ directory back, the linedrawings are screwed up again. If you need more infos, please let me know. Thanks, Greetings and nice Day Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Re: Possible bug in mcedit - Save Options
Hello Cesar, Sunday, January 20, 2008, 5:55:18 PM, you wrote: When I select Options - Save Mode - Quick save it still asks for confirmation everytime I save. This is not a bug. Quick save means that when saving your changes mcedit truncates the original file and writes the new data to it. The behaviour that you seem to need is controlled via: Options - General - Confirm before saving ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Possible bug in mcedit - Save Options
Hello César, On Sun, 20 Jan 2008 16:55:18 +0100 César López Ramírez [EMAIL PROTECTED] wrote: When I select Options - Save Mode - Quick save it still asks for confirmation everytime I save. You'd better look at the editor option: General/Confirm before saving. The Save mode is the way file are (re-)written to the fs, more or less safely, IIRC. Regards, -- wwp signature.asc Description: PGP signature ___ Mc mailing list http://mail.gnome.org/mailman/listinfo/mc
Possible bug in mcedit - Save Options
When I select Options - Save Mode - Quick save it still asks for confirmation everytime I save. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[bug #21873] Conflicting Alt+O keyboard shortcut in mcedit
URL: http://savannah.gnu.org/bugs/?21873 Summary: Conflicting Alt+O keyboard shortcut in mcedit Project: GNU Midnight Commander Submitted by: malvineous Submitted on: Sunday 12/23/2007 at 11:57 Category: Keyboard input Severity: 3 - Normal Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any Release: 4.6.1 Operating System: All ___ Details: When using search and replace in mcedit (F4), pressing Alt+O conflicts between prOmpt on replace and OK, making it impossible to select one of the options. ___ Reply to this item at: http://savannah.gnu.org/bugs/?21873 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel