Bug#1049935: jed: tabs are being inserted by the indent line routine when USE_TABS is off

[Brad Lanam]

You will need to use a larger indent than 3 characters.
It happens to me when the indent is at least 8 characters.
I think these are the relevant variables.

C_INDENT = 2;
C_BRACE = 0;
C_BRA_NEWLINE = 0;
C_Colon_Offset = 2;
variable C_Switch_Offset = 0;
C_CONTINUED_OFFSET = 4;

TAB = 0;
TAB_DEFAULT = 8;
USE_TABS = 0;
Tab_Always_Inserts_Tab = 0;

custom_variable ("Tab_Stops", [1:40] * 2 + 1);

define global_mode_hook (hook_name)
{
  local_setkey ("tab_to_tab_stop", "\t");
}




On Thu, Aug 24, 2023 at 2:05 AM Rafael Laboissière 
wrote:

> Control: tags -1 + unreproducible moreinfo
>
> * Brad Lanam  [2023-08-16 17:59]:
>
> > Package: jed
> > Version: 1:0.99.20~pre.178+dfsg-6
> >
> > I have been using jed for a very long time, and this current release is
> now
> > inserting tab characters when an automatic indent is done (C mode).
> This
> > wasn't the case before.
> >
> > I have  USE_TABS=0 and TAB=0.  The tab key works as I want it to,
> inserting
> > only spaces (I do not have it attached to the indent line hook), but
> when I
> > press the enter key, the indent-line hook executes and tab characters
> are
> > inserted.
> >
> > The enter key / indent line hook did not insert tab characters in
> version :
> > jed 1:0.99.19-8 (debian bullseye).
> >
> >  PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
> >  NAME="Debian GNU/Linux"
> >  VERSION_ID="12"
> >  VERSION="12 (bookworm)"
> >  VERSION_CODENAME=bookworm
> >  ID=debian
>
> Thanks for your bug report, but I am afraid I cannot reproduce this bug.
>
> I am using:
>
>  $ jed --version
>  jed version: pre0.99.20-180/Unix
>  Compiled with GNU C 12.2
>  S-Lang version: 2.3.3
>
>  jed compile-time options:
>   +LINE_ATTRIBUTES +BUFFER_LOCAL_VARS +SAVE_NARROW +TTY_MENUS
>   +EMACS_LOCKING +MULTICLICK +SUBPROCESSES +DFA_SYNTAX +ABBREVS
>   +COLOR_COLUMNS +LINE_MARKS +GPM_MOUSE +IMPORT
>
>  Using JED_ROOT=/usr/share/jed
>
> (from Debian package version 0.99.20~pre.180+dfsg-2)
>
> When I start jed in the following way, with an non-existing file test.c
> (and avoiding my own ~/.jedrc):
>
>  $ jed -n test.c
>
> and I type “int main() {”, I see the following:
>
>  F10 key ==> File   Edit   Mode   Search   Buffers   Windows   System
>  Help
>  int main()
>  {
> █
>
> (where character “█” indicates the prompt)
>
> If I continue typing “int a;“ and the enter key, then I see:
>
>  F10 key ==> File   Edit   Mode   Search   Buffers   Windows   System
>  Help
>  int main()
>  {
> int a;
> █
>
> No tab is inserted, only three spaces before the prompt.
>
> I also tried to start jed without the “-n” option and with this
> minimalistic ~/.jedrc file:
>
>  USE_TABS=0;
>  TAB=0;
>
> but the results are the same.
>
> I will need more information from you, in order to debug this issue.
>
> Best,
>
> Rafael Laboissière
>

Bug#1049935: jed: tabs are being inserted by the indent line routine when USE_TABS is off

[Brad Lanam]

Package: jed
Version: 1:0.99.20~pre.178+dfsg-6

I have been using jed for a very long time, and this current release is now
inserting tab characters when an automatic indent is done (C mode).  This
wasn't the case before.

I have  USE_TABS=0 and TAB=0.  The tab key works as I want it to, inserting
only spaces (I do not have it attached to the indent line hook), but when I
press the enter key, the indent-line hook executes and tab characters are
inserted.

The enter key / indent line hook did not insert tab characters in version :
jed 1:0.99.19-8 (debian bullseye).

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian

Bug#962350: /etc/init.d/checkfs.sh is not very robust, and fails on missing filesystems.

[Brad Lanam]

Package: bugs.debian.org
Severity: normal

/etc/init.d/checkfs.sh is failing on boot and stopping the boot
process.

/etc/init.d/checkfs.sh fails when trying to check a non-existent
filesystem.  Apparently it is trying to run a fsck on a filesystem that was
removed.

As I recall, it fails even when the VFAT filesystem
was present.   I will have to re-create the VFAT filesystem
and see what the log says.


/var/log/fsck/checkfs:

Log of fsck -C -M -A -a
Sat Jun  6 06:51:27 2020

fsck from util-linux 2.33.1
homeMX has been mounted 1 times without being checked, check forced.
homeMX: 131136/41476096 files (7.2% non-contiguous), 39715768/165877760 blocks
open: No such file or directory
fsck.fat 4.1 (2017-01-24)
fsck exited with status code 6

Sat Jun  6 06:51:37 2020



/etc/fstab:
- xfer currently does not exist

# Pluggable devices are handled by uDev, they are not in fstab
UUID=a6b5153a-b005-4ba0-b881-7a03100f80f2 / ext4 defaults,noatime 1 1
UUID=4655-C743 /boot/efi vfat defaults,noatime,dmask=0002,fmask=0113 0 0
UUID=475970aa-a5cf-497d-bfc6-b819830ae21e /home ext4 defaults,noatime 1 2
UUID=415e668d-761b-447b-b3ca-fda9c200cbb6 swap swap defaults 0 0
UUID=149C-3ABF /xfer vfat rw,users,umask=000,noatime 1 2

/ramdisk   /ramdisktmpfs   defaults,size=256m  0 1




[code]

System:
  Host: bll-g7 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
  parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
  root=UUID=a6b5153a-b005-4ba0-b881-7a03100f80f2 ro quiet nosplash
  mem_sleep_default=deep
  Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4
  dm: LightDM 1.26.0 Distro: MX-19.2_x64 patito feo October 21  2019
  base: Debian GNU/Linux 10 (buster)
Machine:
  Type: Laptop System: Dell product: G7 7590 v: N/A serial: 
  Chassis: type: 10 serial: 
  Mobo: Dell model: 0CNDTP v: A01 serial:  UEFI: Dell v: 1.12.0
  date: 02/07/2020
Battery:
  ID-1: BAT0 charge: 58.0 Wh condition: 58.0/60.0 Wh (97%) volts: 16.8/15.2
  model: BYD DELL HYWXJ99 type: Li-poly serial:  status: Full
CPU:
  Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP
  arch: Kaby Lake family: 6 model-id: 9E (158) stepping: A (10)
  microcode: CA L2 cache: 12.0 MiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  bogomips: 62208
  Speed: 900 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 900 2: 900
  3: 900 4: 900 5: 900 6: 900 7: 900 8: 900 9: 900 10: 900 11: 900 12: 900
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
  mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
  IBRS_FW, STIBP: conditional, RSB filling
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: Dell driver: i915 v: kernel
  bus ID: 00:02.0 chip ID: 8086:3e9b
  Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Dell
  driver: nvidia v: 440.36 bus ID: 01:00.0 chip ID: 10de:1f11
  Display: x11 server: X.Org 1.20.4 driver: modesetting,nvidia
  resolution: 1920x1080~144Hz
  OpenGL: renderer: GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 440.36
  direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348
  Device-2: Logitech type: USB driver: hid-generic,snd-usb-audio,usbhid
  bus ID: 1-4.2:7 chip ID: 046d:0a8f
  Sound Server: ALSA v: k4.19.0-6-amd64
Network:
  Device-1: Realtek vendor: Dell driver: r8169 v: kernel port: 3000
  bus ID: 3c:00.0 chip ID: 10ec:2502
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 
  Device-2: Intel Wireless-AC 9260 vendor: Bigfoot Networks driver: iwlwifi
  v: kernel port: 3000 bus ID: 3d:00.0 chip ID: 8086:2526
  IF: wlan0 state: up mac: 
Drives:
  Local Storage: total: 1.14 TiB used: 148.92 GiB (12.7%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: BC501 NVMe 256GB
  size: 238.47 GiB block size: physical: 512 B logical: 512 B
  speed: 15.8 Gb/s lanes: 2 serial:  rev: 80002C00 scheme: GPT
  ID-2: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
  rotation: 5400 rpm serial:  rev: 0D temp: 34 C scheme: GPT
Partition:
  ID-1: / raw size: 19.53 GiB size: 19.10 GiB (97.79%)
  used: 8.28 GiB (43.3%) fs: ext4 dev: /dev/nvme0n1p7
  ID-2: /home raw size: 632.77 GiB size: 621.84 GiB (98.27%)
  used: 140.58 GiB (22.6%) fs: ext4 dev: /dev/sda4
  ID-3: swap-1 size: 20.00 GiB used: 0 KiB (0.0%) fs: swap
  swappiness: 15 (default 60) cache pressure: 100 (default)
  dev: /dev/nvme0n1p9
Sensors:
  System Temperatures: cpu: 59.0 C mobo: N/A gpu: nvidia temp: 46 C
  Fan Speeds 

Bug#734666: di: problems reporting space in NFS mount point

[Brad Lanam]

This problem should be fixed in version 4.41.

Bug#544821: [petr.salin...@seznam.cz: Bug#544821: di: FTBFS on GNU/kFreeBSD]

[Brad Lanam]

Fixed in 4.14



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org