Home » forums » Debian Help Forums: Users Helping Users » GNOME

gvim vs gedit

Tags:

I have noticed that /proc/cpuinfo is shown as empty with gedit but I can read the file with vi, or gvim. I have no idea why?? it's no problem but I would like to know the reason :) thanks to all.

Bookmark/Search this post with:
  • Delicious
  • Digg
  • StumbleUpon
  • Propeller
  • Reddit
  • Magnoliacom
  • Newsvine
  • Furl
  • Google
  • Yahoo
  • Technorati
0
‹ Where's the Debian menu? Etch Audio ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

gvim vs gedit

Submitted by leventguner on Wed, 2007-08-29 15:19.

this is true for other files in /proc too.

»

gvim vs gedit

Submitted by pinniped on Wed, 2007-08-29 18:34.

I can't reproduce that problem on my system. I can't imagine why those files would show up empty in some editors either - I suspect an editor bug. These virtual files and directories behave like ordinary files and directories

»

gvim vs gedit

Submitted by leventguner on Thu, 2007-08-30 02:33.

more strangely, file browser doesn't show the /proc directory contents while root(the waiting mouse icon appears), there is no problem for shell. As a user I can see the files in file browser, but gedit shows the syslog, meminfo etc as empty.. there is no problem in shell neither as user.

What do you think is going on??

»

gvim vs gedit

Submitted by pinniped on Thu, 2007-08-30 03:43.

Perhaps as 'root' the programs are dropping privileges (but I'd still expect to be able to read files). Have you tried to look at those files using the same software but logged in as a normal user?

»

gvim vs gedit

Submitted by leventguner on Thu, 2007-08-30 10:41.

yes I tried, normal user can see the directory, but gedit doesn't show file contents(seem empty).

root doesn't even show the directory in gnome file browser.

there's no problem with shell for both user and root.

»
Syndicate content