Activity for JOE - Joe's own editor
-
Arpad Jakab posted a comment on discussion Help
Select in JOE the line(s) you want to comment out by pressing Ctrl + down/up arrow key. This will highlight the line(s). Press Ctrl+K then C (keep Ctrl pressed). The comment sign (#) should appear at the front of each highlighted line. To uncomment, follow the same procedure, with the key combinations Ctrl+K then U (keep Ctrl pressed)!
-
Duke Normandin posted a comment on discussion Help
Can you show how with sed/awk please!
-
This reply is somewhat late as well. :) I tried your macro using joe' instead ofjmacs'. Your macro seems to only highlight a block, but I may not be using the macro correctly. Would you explain how you use the macro - step-by-step - please. TIA ....
-
Foobar Johnny created ticket #32
Add a commands "fprev" : reversely repeat previous search
-
Egmont Koblinger modified ticket #425
File position reverted by other joe instances
-
Sorry, double post due to network error.
-
File position reverted by other joe instances
-
File position reverted by other joe instances
-
Janvi posted a comment on discussion Help
I tried a installation for Venus what is the Victron Energy Linux System running on ARM Hardware. Configure and make install went through without complaints and jstar starts as normal. Terminal seems not recognizing line wraps cr/lf an there seems other ASCII incompability. Attached is a screendump on what I see. Any idea what went wrong and where to configure?
-
Joe Allen posted a comment on ticket #422
Ah, OK, read too fast. Also, reproducing the bug didn't work for me initially (in Ubuntu 22.04)- I had to run "locale-gen de_DE.UTF-8" first (then it shows up in "locale -k LC_NUMERIC"). Anyway, I see some solutions involving uselocale, but unfortunately it's not universally available. For the number format in the edit buffer, we probably need Ctrl-T options. What often happens with me is that inserted numbers with underscores are not often acceptable. Also, comma is bad news because it's often a...
-
Guenther Brunthaler posted a comment on ticket #422
I'm trying to figure out if using "," in place of "." is a good idea even in locales where that's the norm. I don't think so. This is why my patch does the opposite and allows to use "." as decimal point even in locales where "," is normally the decimal point. The problem is that without the patch, the "." does not work as a decimal point. In order to demonstrate what I mean, invoke joe as follows: $ echo 3.13 0.01 | LC_ALL= LC_NUMERIC=de_DE.UTF-8 joe - Once joe has launched, press [Alt]+[m] to enter...
-
I'm trying to figure out if using "," in place of "." is a good idea even in locales where that's the norm. I guess the problem I have with it is that this is not done in programming languages so I'm not sure it's a good idea in JOE's "math". Hmm.. well I just tried it in Libre Office and it does use "," in de_DE.utf-8.
-
Confirmed. There is a bug in usave.c:saver(). Note the comment: / Last UNDOREC which wasn't modified will be changed * to modified. And because this block is * executed after each 'save', there can't be more * than one record which is not modified * 24 Apr 2001, Marx / What the code should do is set the "changed" flag in all undo records, so if you undo after the save it counts as a change. The assumption in the above comment is wrong- there can be multiple "not modified" points in the undo reco...
-
Undo history weirdness; ^C drops changes without asking for confirmation
-
joe ignores fractional part of numeric literals in some locales
-
Sorry for the very late reply! I don't use emacs, so I am afraid that I won't be able to help you.
-
Matthias S. Benkmann created ticket #421
nmark,abort has side effects
-
John J. Jordan posted a comment on ticket #389
To get the old behavior, comment this out: https://github.com/joe-editor/joe/blob/main/joe/tw.c#L826C2-L831C3 I know that [@jhallen] was debating removing this in a future (?) version.
-
Sorry for spamming this unrelated bug but I've been googling for a while already after trying ChatGPT to get the Ctrl-C behavior fixed and the above comment from years ago is the only thing I found. I NEED CTRL-C TO EXIT EVEN WHEN THERE IS A MARK. I just upgraded from Ubuntu Focal to Noble and this behavior change is KILLING ME. I tried changing the definition of ^C to "nmark,abort" but while that works in the main text screen it breaks Ctrl-C for instance in the "Lose changes to this file (y,n,^C)"...
-
Sorry for spamming this unrelated bug but I've been googling for a while already after trying ChatGPT to get the Ctrl-C behavior fixed and the above comment from years ago is the only thing I found. I NEED CTRL-C TO EXIT EVEN WHEN THERE IS A MARK. I just upgraded from Ubuntu Focal to Noble and this behavior change is KILLING ME. I tried changing the definition of ^C to "nmark,abort" but while that works in the main text screen it breaks Ctrl-C for instance in the "Lose changes to this file (y,n,^C)"...
-
Darren Salt posted a comment on ticket #124
This patch is missing at least one C99 keyword, restrict. (I think that this one should be handled as a storage keyword.)
-
What is dumped into DEADJOE is the contents of all buffers that are not marked as saved. This includes the "yank buffer" as well as histories for file prompts, which are implemented as buffers under-the-hood. It should contain the file contents if the file was modified. If joe crashes or is killed but an open file is not in a dirty state, it won't write out the contents. Is that confirmed to be the case here? And, no none of this is necessarily obvious. Those buffers should probably have better names...
-
Kurt Fitzner created ticket #420
DEADJOE does not represent the file in the editor when it's killed
-
For some time joe's DEADJOE, which used to write out the contents of the file I had in the editor when I, say, lost an ssh connection, no longer does that. Since like Debian 8 or so - whatever joe version that was. Now, it seems to write out a bunch of useless stuff. It says it's stuff that were in in joe, but it appears to be: 1) Unknown users 2) A list of the last 11 files joe was used on 3) A startup log I can find no reference anywhere on what DEADJOE's current behaviour is supposed to be or...
-
Titousensei created ticket #31
Quick open
-
+1 for saving and reloading the list of files in buffers. DEADJOE would be cool too.
-
... (nitpicking) or maybe clear all the bits using Cb &= ~0xC3 and then set the two low ones with Cb |= 3. This is more consistent in the sense that the same bitmask 0xC3 is used throughout the method. Also, I didn't mention it explicitly, but this last paragraph of my previous post explains why "release" events of left scrolling become right scrolling instead, resulting in back-n-forth pairs in some terminals.
-
Update or drop xterm patch and related code
-
Cb contains the button number, as encoded in decimal ASCII as the first parameter if the 1006 extension is supported by the terminal, or the first rawy byte minus 32 with the legacy byte-based protocol if 1006 is not supported by the terminal. Cb's value consists of the following bits: - bit 7 (128): button value bit 3 (8) - bit 6 (64): button value bit 2 (4) - bit 5 (32): drag - bit 4 (16): ctrl - bit 3 (8): alt - bit 2 (4): shift - bit 1 (2): button value bit 1 (2) - bit 0 (1): button value bit...
-
Horizontal mouse scrolling problems and maybe feature req
-
Horizontal mouse scrolling problems and maybe feature req
-
Aspell functions leave alternate screen
-
Build failure due to implicit declaration of functions
-
Reopening in that case.
-
Thierry Moisan posted a comment on ticket #408
This is not yet fixed since #include <util.h> is not imported on mac.
-
Kbd shortcuts commented as "gnome-terminal" are outdated
-
Oh, stupid me. I can finally reliably reproduce. The issue happens when I try to extend the selection too much, beyond the end of the file by pressing Shift+Down at least one too many times. Or the same thing at the top of the file, trying to extend upwards. For some reason, my definititon of these macros differs from the one in the default config, which goes something like rtarw,ltarw,begin_marking,rtarw,toggle_marking ^[ [ 1 ; 5 C Mark right Xterm That right-left (or up-down, etc.) dance at the...
-
See also [#299]
-
As I've written in email, the last major known issues in the coroutine branch were recently resolved in [758cfc] and [d05cc6].
-
As I've written in email, the last major known issues in the coroutine branch were recently resolved in [758cfcf] and [d05cc66].
-
PR #22
-
Taking into consideration [#346], perhaps coroutine - or really, the Windows branch - is the path forwards.
-
Please please pleeeease... :)
-
Let me bump this please. Almost exactly 9 years after reporting this bug, I suspect PuTTY still hasn't changed. The last time I checked (quite a while ago), it was in minimal maintenance mode involving ssh security updates only, nothing about terminal emulation. In the mean time, Windows Terminal has emerged, and with an ssh command also available on Windows, it's an absolutely great, modern replacement for PuTTY, offering many more modern features as well. I'm not asking to remove any feature or...
-
First block copy/move attempt sometimes fails with "No block"
-
C99 restriction
-
C99 formally removed this restriction. GCC hasn't enforced it in a very long time. Until a couple versions ago, MSVC required this but even they have finally updated the C frontend. Twenty-plus years on, I don't think this is much of a concern, unless we see specific build breaks as a result. Closing.
-
I can't reproduce this now that I've implemented a fix for [#409]. It stands to reason that the change of ifhave && !linums to ifhave could fix this, since it would block a lot of unnecessary line updates. Marking duplicate.
-
Screen slow to update with line numbers enabled
-
I can't reproduce this now that I've implemented a fix for #409. It stands to reason that the change of ifhave && !linums to ifhave could fix this, since it would block a lot of unnecessary line updates. Marking duplicate.
-
joe needs a regression test suite
-
This has been in JOE for a while now. It does not cover enough quite yet but the framework is there and proven, imo. Closing.
-
joe-editor.sourceforge.net woefully out of date
-
This needs to be updated to the new git repo, but the site is currently up-to-date so I'm closing this.
-
May be related to the issue addressed in patch 126 or Github PR #16
-
True color derived from terminfo
-
Fixed in git and Mercurial [6babb2]
-
Completion at encoding prompt crashes
-
Completion at encoding prompt crashes
-
Shows "New File" when reading from stdin
-
Setting -rmargin for specific file type
-
Report unrelated to -rmargin; user should fix ftyperc. We do need to fix configuration at some point but that is tracked elsewhere.
-
jmacs help keybindings
-
Merged in Github PR #20
-
Pascal Syntax Highlighting fault
-
This is just due to the extension being used for puppet.
-
Bug with using -lmsg/-rmsg options in ~/.joerc
-
--autoindent still being ignored after 20+ years
-
Closing.
-
Can't read NUL, BEL, BS and DEL from stdin
-
Can't read NUL, BEL, BS and DEL from stdin
-
Can you describe what you mean by working and broken? What scheme is being used? The PHP syntax never references "Var" so that change shouldn't have any effect. Perhaps this is because DefinedIdent isn't rooted on Ident? Does this change have the desired effect: =Variable +DefinedIdent +Ident
-
Unrecognized options: --enable-256-color, --enable-paste64
-
Yes these features are always compiled in. Closing.
-
It's probably worth finding another shortcut for refresh, i think i-search is sticking around.
-
Build failure due to implicit declaration of functions
-
This was fixed in Mercurial and in the new git repo with this commit
-
Rust syntax colouring breakage on ‘r’ and ‘b’
-
I have that applied locally now. No longer seeing the problem.
-
https://github.com/joe-editor/joe/pull/10
-
Rust syntax colouring breakage on ‘r’ and ‘b’
-
John J. Jordan committed [76e07a] on Mercurial
Merge /u/nikic/joe-editor/ branch default into default
-
Port to C99
-
Fix compilation with -Werror=strict-prototypes
-
Looks good.
-
Looks good.
-
I have a candidate fix over on github if you'd like to test. It seems to work but there may be other side-effects I'm not aware of. Wanted to pass along this update, regardless. HTH
-
diego roversi posted a comment on discussion Help
I agree. It's quite useful and I love to see in mainstream joe. I tested the patch and works fine on linux. Thanks in advance.
-
This has been on my radar for a while. Thank you for the clear repro steps.
-
Gary Robinson posted a comment on ticket #409
I just want to add that I experience this problem too. Definitely a bug that should be fixed if anyone is maintaining Joe. I sure do enjoy Joe as an old WordStar guy. It's usually the first thing I install on a new system. This is the only bug I encounter.
-
Bertrando Goio posted a comment on discussion Open Discussion
Hi, I'm a fan of your project. Joe, in particular Jstar ,is my definitive choice for writing but I see that this project is no longer updated. Is it still alive? Are you planning to carry it on? Thank you!
-
Tesf posted a comment on ticket #185
This issue is sixteen years old... but the problem is still there...
-
I was pulling my hair out. I had put up with this for ages when configuring OpenWrt devices over serial. I got fed up today and finally found this. Thanks for posting the solution.
-
Avian Y posted a comment on ticket #29
THANK YOU THANK YOU THANK YOU!!!!!
-
Nikita Popov created merge request #3 on Mercurial
Port to C99
-
Simon Rozman posted a comment on discussion Help
Will this patch get merged eventually? Would love to have this feature out-of-the-box.
-
Werner Karl posted a comment on ticket #343
Good point. However, I found out that the joe_state function can be disabled in the joerc file with --joe_state which is sufficient for my purpose.
-
I'm not sure of the solution to this yet In the meantime I had an idea about that: Why not adding an option to joe that .joe_state is located relative to $XDG_RUNTIME_DIR rather than to $HOME? If $XDG_RUNTIME_DIR is unset or does not point to a valid directory, $HOME can still be used as a fallback. As a workaround to the problem, I have currently taken the following measures in to avoid the security problem: I create a symlink with a known name (say ~/.volatile) in my $HOME directory which points...
-
What is this "joe_state" file good for? It stores things such as the last search expression or the current cursor position within the file edited last. And also the contents of the kill ring. If the information is only valid for the current session One problem here is how to define "session". On your local machine it might be pretty obvious. But what if you are being logged into a remote machine with two different shells at the same time? Depending on the point of view this could be interpreted as...
