Linux Gedit语法高亮显示不工作 我一直用GeDIT用于我的C++和PHP编辑,几个月的语法高亮工作很好。就在最近,我去查看一个.cpp文件,语法突出显示失败。我尝试了多个其他文件,但现在所有文件的语法突出显示都失败了。运行gedit时,我收到以下错误: (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_match_full: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_replace_eval: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: g_regex_unref: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_match_full: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_replace_eval: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: g_regex_unref: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_match_full: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_replace_eval: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: g_regex_unref: assertion `regex != NULL' failed (gedit:9833): GtkSourceView-WARNING **: in file /usr/share/gtksourceview-2.0/language-specs/cpp.lang: style 'c:keyword' not defined (gedit:9833): GtkSourceView-WARNING **: Failed to load '/usr/share/gtksourceview-2.0/language-specs/cpp.lang': style override used with wildcard context reference in language 'cpp' in ref 'def:line-continue'

Linux Gedit语法高亮显示不工作 我一直用GeDIT用于我的C++和PHP编辑,几个月的语法高亮工作很好。就在最近,我去查看一个.cpp文件,语法突出显示失败。我尝试了多个其他文件,但现在所有文件的语法突出显示都失败了。运行gedit时,我收到以下错误: (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_match_full: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_replace_eval: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: g_regex_unref: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_match_full: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_replace_eval: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: g_regex_unref: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_match_full: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: PCRE library is compiled without UTF8 support (gedit:9833): GLib-CRITICAL **: g_regex_replace_eval: assertion `regex != NULL' failed (gedit:9833): GLib-CRITICAL **: g_regex_unref: assertion `regex != NULL' failed (gedit:9833): GtkSourceView-WARNING **: in file /usr/share/gtksourceview-2.0/language-specs/cpp.lang: style 'c:keyword' not defined (gedit:9833): GtkSourceView-WARNING **: Failed to load '/usr/share/gtksourceview-2.0/language-specs/cpp.lang': style override used with wildcard context reference in language 'cpp' in ref 'def:line-continue',linux,syntax,highlighting,opensuse,gedit,Linux,Syntax,Highlighting,Opensuse,Gedit,这是一个最近才开始出现的令人沮丧的问题,我不知道为什么 其他信息: 我没有根访问权限 我的机器正在运行openSUSE 11.3 gedit版本:2.28.3 pcretest命令返回:PCRE版本7.6 2008-01-28 我已经多次重启,希望它能自行修复,但运气不佳 我将非常感谢任何关于这个问题的帮助或想法。经过一番周折,终于解决了我的问题。我使用的程序涉及编辑我的LD_LIBRARY_PATH环境变量,因此我在.cshrc中添加了几行,以添加一些共享库。我确保将我新添加的库附加到变量

这是一个最近才开始出现的令人沮丧的问题,我不知道为什么

其他信息:

  • 我没有根访问权限
  • 我的机器正在运行openSUSE 11.3
  • gedit版本:2.28.3
  • pcretest命令返回:PCRE版本7.6 2008-01-28
  • 我已经多次重启,希望它能自行修复,但运气不佳

我将非常感谢任何关于这个问题的帮助或想法。

经过一番周折,终于解决了我的问题。我使用的程序涉及编辑我的LD_LIBRARY_PATH环境变量,因此我在.cshrc中添加了几行,以添加一些共享库。我确保将我新添加的库附加到变量中,但无论出于何种原因,这仍然破坏了Gedit进行语法高亮显示的能力。从.cshrc脚本中取出setenv命令后,我重新启动,Gedit的语法高亮显示恢复正常

我听说使用LD_LIBRARY_PATH被认为是不好的做法。现在,我对可能出现的问题有了第一手的经验