[SOLVED] Gedit and Kate's serious troubles in C++.

AlexBB · 10-13-2015, 03:31 PM

John_W, please do not make extreme assumptions. The Gfortran code is all in local files in one directory. All files have .f90 extension. While developing this program I used gedit editor, nothing else. I've had little trouble. I compiled everything. There are some high level problems that I could not resolve and I had to rethink the fortran because none of my potential consultants wants to mess with fortran. They all want C++. My overall fortran code is perhaps 5,000 lines long, maybe more. It is all about special functions. I initially made a decision to do it in fortran and now regret. Actually I had to convert some C++ code into fortran, for instance this: Librow FFT. Now I will use the original but that FFT code is a very small part of overall package. There is something in C++ code, apparently, that causes all these problems. I read two days ago (cannot find now where) that anjuta was designed specifically for C++. Very hard o believe. - Alex

mchroman · 10-14-2015, 10:20 AM

I would go to VI asap. I also use qtcreator for c++. It is an IDE and works pretty well. You will need to set up the kits in qtcreator and, if done properly, you can ssh debug through the qtcreator IDE. I have never seen anything that resembles your issue but hope this helps.

VI first...then qtcreator

AlexBB · 10-14-2015, 05:01 PM

Thank you, mchroman. You know I even bought a brand new mouse and replaced the old one with no effect whatsoever. Yes, I've switched to vim. - Alex

John VV · 10-14-2015, 08:16 PM

Quote:

please do not make extreme assumptions.

that is based on real life issues i have had with websites

the odd text formatting in some lines of code need REEDITING to rearrange it

as sgosnell mentioned
then something is very wrong with your hardware if BOTH Gedit and kate AND the editor in ajunta are all doing that

have you ram a ram test recently
you might have a bad ram card

AlexBB · 10-17-2015, 10:36 AM

John_w thanks,

A new development. Take a look. I enter the command: $vim sphere_perspective.cpp

It gives me this output:

Code:

E325: ATTENTION
Found a swap file by the name ".sphere_perspective.cpp.swp"
          owned by: alex   dated: Mon Oct 12 09:23:53 2015
         file name: ~alex/GFORTRAN-APPS/SPHERE-DESIGN/sphere_perspective.cpp
          modified: YES
         user name: alex   host name: alex-HP-ProBook-6555b
        process ID: 3323
While opening file "sphere_perspective.cpp"
             dated: Sun Oct 11 18:51:06 2015

(1) Another program may be editing the same file.  If this is the case,
    be careful not to end up with two different instances of the same
    file when making changes.  Quit, or continue with caution.
(2) An edit session for this file crashed.
    If this is the case, use ":recover" or "vim -r sphere_perspective.cpp"
    to recover the changes (see ":help recovery").
    If you did this already, delete the swap file ".sphere_perspective.cpp.swp"
    to avoid this message.

Swap file ".sphere_perspective.cpp.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:

I cannot find the file sphere_perspective.cpp.swp in this directory. As far as I know there is no other program editing the same file. What is it all? Some kind of Halloween joke?

What shall I do? Anybody with experience with this, please help.

Thanks, - Alex

astrogeek · 10-17-2015, 01:36 PM

Look a little more closely...

Code:

Found a swap file by the name ".sphere_perspective.cpp.swp"

The filename has a leading dot, so it is a hidden file. You can see it with...

Code:

ls -a

Vim creates a temporary working file with this name format each time you open a file, and uses it to incrementally save your changes. Then, if your system is shutdown without closing the session, or if you have a power outage, for example, you can recover your work.

When you close a file the real file is updated and the swp file is removed.

So you must have shutdown with a vim session still open, or you are trying to open it in two editor sessions concurrently.

Easy fix - just read the options and tell it what you want it to do.

AlexBB · 10-17-2015, 06:13 PM

Astrogeek thank you,

Of course I read the options but since it was the first time I saw this (I've used VIM before for quite a while) I was very cautions and decided to ask for explanations. I really appreciate your help. Thanks, - Alex

debguy · 10-20-2015, 01:11 PM

Instead of pasting it in one place it would do it in numerous places

make sure others experience the same issue before assuming you are right that gedit needs dbg / debugging.

why: a bad mouse button can cause pasting in (2? more) places. bad mice are common.

AlexBB · 10-22-2015, 04:38 PM

I bought a new mouse (I mentioned it before in this thread) and nothing changed. It was a mouse from Best Buy, I think a reputable place; as I said nothing has changed.

astrogeek · 10-22-2015, 04:45 PM

Do I understand that it still happens in Vi/Vim?

As mentioned in earlier posts, I have to suspect hardware at this point.

Top suspect would be RAM, followed by a possible motherboard problem.

Have you run memtest86 on it? If not I would start there with a good long run.