Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

1 votes
0 answers
19 views
.jsf (JOE editor) syntax highlighting for todo.txt
I can't get the JOE editor to highlight tags like ``due:YYYY-MM-TT`` for due dates or ``rec:NP`` for recurrences to work; I was able to highlight prioritized tasks though. * A sample `todo.txt` looks like this: ```text update the ad with Sara (B) ask Richard about stuff send questions to Mr K next w...
I can't get the JOE editor to highlight tags like `due:YYYY-MM-TT for due dates or rec:NP` for recurrences to work; I was able to highlight prioritized tasks though. * A sample todo.txt looks like this:
update the ad with Sara
    (B) ask Richard about stuff
    send questions to Mr K next week
    (B) ask T about integration for A
    (A) test 1110 due:2024-12-09 rec:1d
    test 1120 due:2024-12-09 rec:1w and tell S
* I'm trying to highlight the prioritized tasks and the tags with this todotxt.jsf:
# Todo.txt syntax highlighting for JOE
    
    =Idle
    =Prio    CYAN    bold
    =Due    bg_MAGENTA
    =Rec    bg_YELLOW
    
    :lineStart Idle
      *    idle    buffer
      "("    prio    noeat    buffer
    
    :idle Idle
      *    idle    buffer
      " :"    tagwordsIdle    hold
      "\n"    lineStart
    
    :prio Prio
      *    prio    buffer
      " :"    tagwordsPrio    hold
      "\n"    lineStart
    
    :tagwordsIdle Idle
      *    idle
      "\n"    lineStart    strings
      "due"    dueIdle    recolor=-2
      #"rec"    recIdle
    done
    
    :tagwordsPrio Prio
      *    prio
      "\n"    lineStart    strings
      "due"    duePrio    recolor=-2
      #"rec"    recPrio
    done
    
    :dueIdle Due
      *    dueIdle
      " \t"    idle
    
    :duePrio Due
      *    duePrio
      " \t"    prio
How would I highlight individual tags/words within a line?
montionoimi (11 rep)
Dec 9, 2024, 03:11 PM • Last activity: Dec 10, 2024, 11:09 AM
1 votes
1 answers
142 views
How to make joe editor start from the very first line on commits?
I upgraded the system (to openSUSE 15.3) and I noticed that now when I commit something using git or svn, when I am about to enter some comment (I set joe as editor) the caret is not placed at the very first line, but at the first comment made by git/svn. I don't like this behaviour, so how can I ma...
I upgraded the system (to openSUSE 15.3) and I noticed that now when I commit something using git or svn, when I am about to enter some comment (I set joe as editor) the caret is not placed at the very first line, but at the first comment made by git/svn. I don't like this behaviour, so how can I make joe to put caret in the first line? **Update** Git example. After issuing "git commit", editor is launched and I can add comment here. This is actual result (it is just the beginning of commit text):
|# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
And this is what I would expect (and it worked this way previously):
|
# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
"|" here denotes cursor/caret, it is not an actual character. The first line is an empty one. **Update 2** snv, again showing just begining. Actual behaviour:
|--This line, and those below, will be ignored--
Expected/previous behaviour:
|
--This line, and those below, will be ignored--
**Update 3**: I tested mcedit against both svn and git, in both cases I got behaviour as expected -- i.e. caret/cursor was placed in very first line. Ad I leave it this way (i.e. mcedit as editor) and today, after several successful commits, mcedit also shown the file with cursor/caret in the second line (so incorrectly).
greenoldman (6496 rep)
Jan 8, 2022, 03:31 PM • Last activity: May 16, 2024, 11:03 AM
1 votes
1 answers
138 views
How to set encoding in editor joe based on file type
I want Java properties files (*.properties) to be opened in ISO8859-1 encoding on my otherwise UTF-8 using linux. Found the ftype.rc, but cannot found out how to configure it.
I want Java properties files (*.properties) to be opened in ISO8859-1 encoding on my otherwise UTF-8 using linux. Found the ftype.rc, but cannot found out how to configure it.
Daniel (798 rep)
Jun 22, 2022, 10:37 AM • Last activity: Jul 2, 2022, 06:51 AM
2 votes
1 answers
289 views
"joe" on Debian 11
I have a fresh cloud server with Debian 11 and am trying to install my favorite litte editor `joe`, but cannot find it: root@serv:~# apt-cache search joe root@serv:~# apt install joe Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate...
I have a fresh cloud server with Debian 11 and am trying to install my favorite litte editor joe, but cannot find it: root@serv:~# apt-cache search joe root@serv:~# apt install joe Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package joe root@serv:~# uname -a Linux serv 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux I remember doing it on some other machine (maybe Debian 10?) and it worked. Can anyone help?
cxxl (131 rep)
Sep 1, 2021, 03:44 PM • Last activity: Sep 1, 2021, 03:48 PM
4 votes
1 answers
808 views
Joe 4.6: How do I override color definitions?
After upgrading from Debian 9 (Joe 4.4) to Debian 10 (Joe 4.6), the following lines in my joerc started creating errors: ``` =Preproc yellow =Tag cyan bold ``` I used this to override the default colour scheme, which has C pre-processor lines in dark blue, which is very difficult to read when using...
After upgrading from Debian 9 (Joe 4.4) to Debian 10 (Joe 4.6), the following lines in my joerc started creating errors:
=Preproc    yellow
=Tag    cyan bold
I used this to override the default colour scheme, which has C pre-processor lines in dark blue, which is very difficult to read when using a terminal with black background. I am unable to find documentation on how to do this in 4.6, the entire section on colours has just disappeared from the default /etc/joerc. Any help would be appreciated.
nafmo (145 rep)
Aug 22, 2019, 07:52 AM • Last activity: May 5, 2021, 04:34 PM
0 votes
1 answers
84 views
JOE and ftyperc
Is there a way to set, for example, the right margin for all files in a specific directory? For example, set the right margin to 125 for all files in `$HOME/bin` but leave the default for files in `$HOME/Mail`. I've tried lots of things and cannot get any to work.
Is there a way to set, for example, the right margin for all files in a specific directory? For example, set the right margin to 125 for all files in $HOME/bin but leave the default for files in $HOME/Mail. I've tried lots of things and cannot get any to work.
am_dew (1 rep)
Mar 2, 2021, 04:46 PM • Last activity: Mar 3, 2021, 12:23 AM
2 votes
1 answers
277 views
How to set joe to disable word wrap for *.R files?
What do I put in .joerc to disable word wrap for *.R files?
What do I put in .joerc to disable word wrap for *.R files?
Tomas (217 rep)
Jan 26, 2020, 08:49 PM • Last activity: Jan 27, 2020, 01:24 PM
2 votes
1 answers
748 views
joe (editor) global vs. local options on the command line?
joe (Joe's Own Editor) manual outlines the command syntax like so: joe [global-options] [ [local-options] filename ]... My question is, how do I demarcate **global-options** from **local-options**? An example: joe --wordwrap -nobackup file1 file2 file3 Even though I placed `--wordwrap` (to turn word...
joe (Joe's Own Editor) manual outlines the command syntax like so: joe [global-options] [ [local-options] filename ]... My question is, how do I demarcate **global-options** from **local-options**? An example: joe --wordwrap -nobackup file1 file2 file3 Even though I placed --wordwrap (to turn wordwrap off), and -nobackup (to turn backup file creation off), they only apply to the first file. The subsequent files, *file2* and *file3*, still will have word wrap on, and backup files will be created for them if edited and saved. Of course I could do this: joe --wordwrap -nobackup file1 --wordwrap -nobackup file2 --wordwrap -nobackup file3 .. but that is cumbersome, and would imply there wouldn't be **global-options** at all. I could also edit /etc/joe/joerc and /etc/joe/ftyperc (or copy them to the user's home dir, and make the overriding edits there) to turn word wrap and backups off for all files, but on systems where I'm only visiting (and that might have, say, a shared **/home/ubuntu** user/homedir, say, rather than individual user accounts/homedirs), I would rather not make permanent changes to the system tools that other users might use, yet it would be handy to be able to enter the editor args on the command line (perhaps even via a keyboard macro) without having to repeat the args for each file. So is there a way to have **global-options** in joe on the command line for parameters that can be also used as **local-options**? ("Why don't you use Vi[m] or Emacs instead?" Because I've never found vi[m] intuitive, I have forgotten the Emacs chords which I had mastered in the 90's, and joe does the job nicely, so why not? :-)
Ville (351 rep)
Jan 10, 2017, 05:55 AM • Last activity: Jan 10, 2017, 11:36 PM
6 votes
3 answers
7005 views
Joe's own editor: changing syntax highlighting
Unfortunately, when I try to edit an XML, trying to read that dark blue against black is murder. I am amazed that Googling "joe editor change highlighting" returns nothing! Is it really impossible to change the colours, while using the binary that came w/the RPM? I'm using joe 3.1
Unfortunately, when I try to edit an XML, trying to read that dark blue against black is murder. I am amazed that Googling "joe editor change highlighting" returns nothing! Is it really impossible to change the colours, while using the binary that came w/the RPM? I'm using joe 3.1
Opux (227 rep)
Sep 19, 2014, 06:56 PM • Last activity: Dec 22, 2016, 01:04 PM
1 votes
2 answers
251 views
using git to version-control any file edited with my text editor
Is there any way to integrate text editor (`joe` in my case) with `git` in such a way, that every change to any file is automatically committed in git (probably with a time stamp), so that I can always go back (revert changes) or diff changes of any files which I have edited? I don't even know how t...
Is there any way to integrate text editor (joe in my case) with git in such a way, that every change to any file is automatically committed in git (probably with a time stamp), so that I can always go back (revert changes) or diff changes of any files which I have edited? I don't even know how that would work. Possibly with some wrapper script ?
Martin Vegter (598 rep)
Oct 30, 2015, 06:28 PM • Last activity: Mar 15, 2016, 01:00 PM
1 votes
0 answers
669 views
.jsf syntax highlighting file (for joe editor)
I am trying to modify the .jsf syntax highlighting file for the `joe` editor `/usr/share/joe/syntax/ini.jsf`. This file contains rules for highlithing/coloring `ini` files. For `ini` files, anything after ";" should be a comment. ; comment key = value ; comment the above works OK, and `joe` colors e...
I am trying to modify the .jsf syntax highlighting file for the joe editor /usr/share/joe/syntax/ini.jsf. This file contains rules for highlithing/coloring ini files. For ini files, anything after ";" should be a comment. ; comment key = value ; comment the above works OK, and joe colors everything after ";" green. However, id does not work correctly in following case: key = value ; comment In other words, it only works when there is only one space in front of the ";". I would like to fix this, but I am struggling with the syntax file structure. Following is a snippet of the relevant part of /usr/share/joe/syntax/ini.jsf: :line_start Idle * key noeat "\n" line_start " \t\r" line_start # leading spaces ";#" line_comment recolor=-1 :line_comment Comment * line_comment "\n" line_start **Can somebody please suggest how to make the necessary modification?**
Martin Vegter (598 rep)
Mar 11, 2015, 11:45 AM
3 votes
1 answers
196 views
Bind Ctrl+Down in Joe on a Linux console
When I want to select a line in `joe` editor, I can go to the beginning and simply pres CTRL-Down and this will select the line. I can move somewhere ales and copy the line with CTRL-k-c . The key code corresonding to CTRL-Down is `^[[1;5B` and I see this is defined in joe's config file `/etc/joe/jo...
When I want to select a line in joe editor, I can go to the beginning and simply pres CTRL-Down and this will select the line. I can move somewhere ales and copy the line with CTRL-k-c. The key code corresonding to CTRL-Down is ^[[1;5B and I see this is defined in joe's config file /etc/joe/joerc: dnarw,uparw,begin_marking,dnarw,toggle_marking ^[ [ 1 ; 5 B Mark down The above described works when I am in a virtual terminal, i.e. terminator. When I am in a console (i.e. CTRL-ALT-F2, it does not work anymore. Moreover, I have noticed that when I pres CTRL-Down in console, I get another code: ^[[B. I am using console a lot and I would like to have the possibility to use the "Mark Down" feature. Is there any way to do it?
Martin Vegter (598 rep)
Oct 2, 2014, 01:35 AM • Last activity: Oct 6, 2014, 12:06 PM
2 votes
1 answers
486 views
Move line in Joe's Own Editor
Is there a way to move a line up and down in the [joe][1] editor? [1]: http://en.wikipedia.org/wiki/Joe%27s_Own_Editor
Is there a way to move a line up and down in the joe editor?
Simon Warta (125 rep)
Sep 9, 2014, 10:28 AM • Last activity: Sep 10, 2014, 01:55 PM
Showing page 1 of 13 total questions